Bug fixes

• Fixed haddock for the Language.PureScript.Bundle module Fix the haddock for the Language.PureScript.Bundle module #1262 (@wuzzeb)
• Some erroneous error positions were fixed for kind and missing instance errors Error messages where the location information is incorrect or misleading #1086 (@garyb)
• The number of warnings printed for exhaustivity checks was limited to 5 Exhaustivity hangs compiler #1281 (@nicodelpiano)
• Home directory is checked for .psci file after the current working directory Look for a .psci file in the user's home directory #883 (@mjgpy3)
• Line numbers now show for shadowed name warnings Warnings have no line numbers #1165 (@nicodelpiano)
• Cabal file was fixed for Nix packaging nix fails to build from cabal package #1302 (@MasseGuillaume)
• Kind query for types defined in psci now works Kind query in psci fails for types defined in the session #1235 (@mjgpy3)
• Boolean operations are now being inlined again Optimizer rules broken after BooleanAlgebra change #1312 (@garyb)
• Int operations are now being inlined again Int inlining is not working #1330 (@garyb)
• "Writing..." and "Compiling..." messages are no-longer printed in psci PSCi has started printing "Writing..." and "Compiling..." messages again #1276 (@paf31)

Enhancements

• Exhaustivity checker was extended to report errors about redundant cases Overlapping patterns #1289 (@nicodelpiano)
• Improved triggering of suggestion for errors about using (<<<) instead of (.) Only make composition suggestion on object . app function #1284 (@mjgpy3)
• Only show the module name rather than the filename for pattern errors Don't show file name in pattern match errors #1296 (@nicodelpiano)
• Error reporting in psc-bundle was improved Improved error reporting in psc-bundle #1307 (@hdgarrood)
• psc-publish code is now part of the library module Move psc-publish code into the library #1304 (@hdgarrood)
• psc-publish now has --version and --help options Add --version and --help options to psc-publish #1300 (@garyb)
• psc-publish now has a --dry-run option for checking whether the module can be published Add --dry-run option to psc-publish #1308 (@hdgarrood)
• psc-publish now requires a clean working tree Should psc-publish refuse to run if the working tree is dirty? #1306 (@hdgarrood)
• psc-publish can now find bower on Windows machines psc-publish cannot find bower on Windows #1317 (@hdgarrood)
• psc-publish now uses OS-specific path delimiters to fix another bug on Windows psc-publish produces nothing on Windows #1326 (@hdgarrood)
• Error list heading was made emacs-friendly Make error list heading emacs-friendly #1327 (@epost)

That covers every PR we merged aside from the test-related ones as I figured that's externally invisible (thanks though @hdgarrood!)

Thanks for putting this together :)

No problem!

👍 I agree, I don't think the test stuff should go into the release notes either.