Opening this issue to keep track of core library updates for 0.14. I've managed to get @garyb's purescript-dependency-helper running again (see https://github.com/hdgarrood/purescript-dependency-helper) so that I could produce this list. The list is topologically sorted so that if we update the libraries in this order, any library we start working on should already have had its dependencies updated.
I think the procedure for each library should be more or less this:
- Update .travis.yml to grab the most recent RC (see eg purescript/purescript-prelude@268870d)
- If there's already an 0.14 branch, merge that into master
- Temporarily update bower.json to pull the master versions of all dependencies
- Make sure
psa in package.json is on v0.8.0 or newer (because of the stderr/stdout changes)
- Merge any outstanding PRs with breaking changes
- Look over the issues to see if there are any breaking changes we want to do now
Once we have v0.14.0 tagged, we should go back over all of these libraries in the same order and do the following for each:
- Revert the changes to .travis.yml so that the most recent compiler version is pulled in
- Update dependencies in bower.json to specify real version ranges, rather than master
- Tag a version and update the package-sets repo
Opening this issue to keep track of core library updates for 0.14. I've managed to get @garyb's purescript-dependency-helper running again (see https://github.com/hdgarrood/purescript-dependency-helper) so that I could produce this list. The list is topologically sorted so that if we update the libraries in this order, any library we start working on should already have had its dependencies updated.
I think the procedure for each library should be more or less this:
psain package.json is on v0.8.0 or newer (because of the stderr/stdout changes)Once we have v0.14.0 tagged, we should go back over all of these libraries in the same order and do the following for each:
Bifunctornewtypes where appropriate purescript-profunctor#23)