Skip to content
This repository has been archived by the owner on Jan 20, 2020. It is now read-only.

Request: Canary version #297

Closed
sfkiwi opened this issue Apr 1, 2018 · 1 comment
Closed

Request: Canary version #297

sfkiwi opened this issue Apr 1, 2018 · 1 comment

Comments

@sfkiwi
Copy link
Contributor

sfkiwi commented Apr 1, 2018

Would it be possible to have a canary release of the library any time a PR is merged into master? Similar to how chaijs does it? chaijs/chai#751

That way you can use the @canary tag to specify you want the bleeding edge build. For small changes this would speed up development instead of having to wait for the next official release.

@rmm5t
Copy link
Contributor

rmm5t commented May 15, 2018

Interesting concept, but to me, this doesn't sound like the best approach for a project like gdax-node. Also, it doesn't look like chai adopted their canary releases. i.e. They haven't had a canary release in over a year.

Instead, for "bleeding edge," I would recommend just referencing the master branch directly.

npm install coinbase/gdax-node

I'd also like to make it a plan for the future (if possible) that we publish releases more frequently here as well, so some of this becomes moot to some degree.

@rmm5t rmm5t closed this as completed May 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants