Releases · purescript/psc-package (original) (raw)

v0.6.2

Updated the cabal file version.

v0.6.1

This version bumps the Stack LTS version: #160

This also targets a related issue with Windows users not being able to use package sets due to some newline issues: #157. Please file a new issue if you run into issues with this release. This issue most likely only affects users with specific newline settings in their gitconfig, so if you did not have an issue before, you should be fine now.

v0.6.0

This release brings the ability to use local package sets by using a filepath for "source". See more here: #158

Note that if you are already using some form of local package sets, you should update your "source" attribute to point to your packages.json, whether it be in the project root as packages.json, .psc-package/local/.set/packages.json, or elsewhere.

v0.5.1

Bumps the version number of Psc-Package executable

v0.5.0

This release fixes the Windows purs finding problem #141 (@taiju)

v0.4.2

v0.4.1

• Adds warnings for trying to install packages without (#126 by @Dretch)
• Filters "installing" messages for build (#130 by @Dretch)
• Adds options for limiting jobs for install (#127 by @Vladciobanu)

v0.4.1-pre

Adds limiting git process jobs #127 and gives warnings for failed installations with purescript- prefixes #125

v0.4.0

Per #121, removes the confusing misfeature "add-from-bower", which led to many users thinking this command was for adding "extra-deps" like Stack. See the thread for details on how you could readily replace this command if you used it before.

v0.3.4-pre

sort dependencies when writing out package sets and config (#118)