Skip to content

add release notes to a wiki #70

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.

Sign up for GitHub

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

Open
mitch-mitchel wants to merge 1 commit into
base: develop
Choose a base branch
from
Open

add release notes to a wiki #70

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions wiki/A2J Deps Release.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
## A2J Deps Release:
- Change to the `develop` branch if not already on it.
- Do a `git pull` to make sure you are up to date with all changes.
- Make sure you are logged into `npm`. In your terminal type `npm whoami` and be sure you have permissions to do npm releases with that account for this repo.
- Run `npm run release:<semverType>` where `<semverType>` could be either `patch`, `minor`, or `major`. Example, for a bug fix that is not a breaking change, you would run `npm run release:patch`.
- This will execute the release script, running the tests first (a release will not happen with failed tests)
- Once the npm release is successful, do a pull request from `develop` into `production` to keep it in parity with the npm release.
- OPTIONAL -> Update Author, Viewer and/or A2J DAT to this new release as needed. aka `npm install @caliorg/a2jdeps@latest` which will update both the package.json file and the package-lock.json to this latest release version in the respective codebase.