Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: automatically publish to npmjs @next tag on push to master #605

Open
vojtechsimetka opened this issue Mar 31, 2022 · 2 comments
Open
Labels
kind:enhancement A net-new feature or an improvement to an existing feature type:issue

Comments

@vojtechsimetka
Copy link
Contributor

This has been discussed on our roundtable on March 31st. Here is a dump of the proposal:

  • rationale
    • we are anyways claiming that master always works
    • this truly gives the right weight to the bee-js@next idea and ppl (including us) being able to test it
  • proposal
    • add ci action that does a pre-release to npmjs automatically on each merge to master
    • remove the manual pre-release mechanism
@vojtechsimetka vojtechsimetka added the kind:enhancement A net-new feature or an improvement to an existing feature label Mar 31, 2022
@AuHau
Copy link
Contributor

AuHau commented Mar 31, 2022

Sounds good to me 👍

I am just wondering if it does not make sense still to keep the pre-release mechanism? Maybe for "release candidates" testing?

@vojtechsimetka
Copy link
Contributor Author

Yes but then probably it should be extended to have a functionality to provide specific commit to build from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:enhancement A net-new feature or an improvement to an existing feature type:issue
Projects
None yet
Development

No branches or pull requests

2 participants