8000 Update development.md · rxmarbles/github-script@2d40ba5 · GitHub
[go: up one dir, main page]

Skip to content

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit 2d40ba5

Browse files
authored
Update development.md
1 parent 3c58ce3 commit 2d40ba5

File tree

Collapse file tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/development.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ well.
2222

2323
Releases are done manually, for now:
2424

25-
1. Ensure that the build is up to date with `npm run build`.
26-
1. Bump the [package.json](/package.json#L3) and [package-lock.json](/package-lock.json#L3) version numbers and commit them.
25+
1. Ensure that the build is up to date with `npm run build`. It's also good to ensure you have the correct dependencies installed by running `npm install` before you build.
26+
1. Bump the [package.json](/package.json#L3) and [package-lock.json](/package-lock.json#L3) version numbers and commit them. I like to do this with `npm version {major,minor,patch} --no-git-tag-version`. This will bump the version numbers but let you manually commit and tag, yourself.
2727
1. Update documentation (including updated version numbers).
28-
1. Tag main with the new version number and create a GitHub release.
28+
1. Tag main with the new version number and create a GitHub release. Make sure you also force-create and force-push tags for minor and patch updates. For example, when creating v5.1.0 (a minor bump), you want to create (or update) `v5`, `v5.1`, and `v5.1.0`.

0 commit comments

Comments
 (0)
0