"pulp release"

[purescript-contrib]

"pulp release"

[bodil]

I still think it might be wiser to keep the version and release commands distinct. Particularly in situations where git push fails for whatever reason, where you don't want to bump the version again to retry, and also just as a safety net for the user.

npm stores an auth token locally after requesting the user's npmjs.org credentials. It has a login command for this purpose, which also allows you to log in as another user by re-running it. We may want to replicate this as well.

So,

• pulp login generates an auth token for Pursuit.
• pulp version does the bump, but only if psc-publish doesn't object.
• pulp publish (or pulp release? I'm just following npm's lead here) publishes the package to Bower (ie. git push, and we might actually want to run bower register here too?) and Pursuit.

[hdgarrood]

Sounds good. I'll take a look at this after I've done the --dry-run option for psc-publish. Following npm's lead with the command names does seem sensible, and also I think publish describes the second stage better than release does (if we're splitting it into two stages). Also 👍 for bower register.

[tfausak]

👍

[damncabbage]

Just following up from the chat with @hdgarrood in IRC; I'm having a crack at the above.

[paf31]

👍 I'd love to see this, since I often forget to upload docs to Pursuit right now. I'll help out if I can, but I need to get up to speed on the Pulp source first.

[tfausak]

I would love to see this too. For what it's worth, you can automatically generate documentation on Travis CI: http://taylor.fausak.me/2015/11/15/automatically-generate-purescript-documentation/