chore: Describe release/publish steps#358
Merged
Merged
Conversation
- added `np` as a devDepedency - added npm script `release` to make it easier to remember - added npm script `version`/`changelog-has-version.sh` to make sure version is described in CHANGELOG.md
- added script `changelog` to add "Unreleased" section to changelog, so it can be tweaked manually - `auto-changelog` is invoked using npx, so it's not a devDependency https://github.com/CookPete/auto-changelog
karfau
added
documentation
# Conflicts: # package-lock.json # package.json
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since I was having a hard time remembering all the steps we did previously I wanted to document them. So I did that while doing the 0.8.0 release.
I also decided to add the tools that we are using for this to the devDependencies, to speed up things and pin the versions/make them transparent.
After describing all the release steps I discovered that this would also be a good place to describe how the project currently prioritizes issues and PRs.