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

Discuss/Setup NPM Release Process #118

Open
rvenables opened this issue Apr 21, 2023 · 2 comments
Open

Discuss/Setup NPM Release Process #118

rvenables opened this issue Apr 21, 2023 · 2 comments
Assignees
Milestone

Comments

@rvenables
Copy link
Collaborator

rvenables commented Apr 21, 2023

It would be helpful to have an established NPM release process. Initial open questions for discussion:

  • Should we automate the NPM package release process? If so, how should it be triggered?
  • Should we have a test / prerelease NPM package version?
  • Should we adopt a versioning strategy (like https://semver.org/)
@rvenables rvenables added this to the Leaving Alpha milestone Apr 28, 2023
@rvenables
Copy link
Collaborator Author

@caravansteve talked about writing up some options and suggested direction on the community development call (http://chat.opr.dev/) on 6/9.

@caravansteve
Copy link
Collaborator

From Benjamin Coe at Google:

With regards to publishing, you may still consider automating this process to limit the # of users with access on npm -- you might look at release-please, which I have setup for my open source project yargs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants