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
Add publish/release instructions #148
Conversation
CONTRIBUTING.md
Outdated
|
||
### Major / Minor Versions | ||
|
||
1. Set the version: `npm version minor` or `npm version major` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You most likely usually want npm version patch
or npm version minor
. I suspect it will be a while before we do a 2.0.0.
CONTRIBUTING.md
Outdated
|
||
### Patch Version | ||
|
||
For a critical fix, we can `git checkout` a previous release and cherry-pick or apply specific changes. This is especially useful for security releases and if there are already some bigger changes in the master branch and you don't want to push a normal release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also useful if there's a security fix and we want to patch multiple minor versions. 1.0.0 -> 1.0.1 and 1.1.0 -> 1.1.1 for example.
CONTRIBUTING.md
Outdated
|
||
## Releasing | ||
|
||
Note: We use `publish-release` for some pre-publish confidence checks to avoid common mistakes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should add some details about the prepareConfig:publish
and why we use prepack
for it.
Including considerations for config and clearer details on patching.
No description provided.