You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+12-6Lines changed: 12 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -221,12 +221,18 @@ The following are instructions for updating [highlight.js](https://highlightjs.o
221
221
222
222
Instructions for mdBook maintainers to publish a new release:
223
223
224
-
1. Create a PR to update the version and update the CHANGELOG:
225
-
1. Update the version in `Cargo.toml`
226
-
2. Run `cargo xtask test-all` to verify that everything is passing, and to update `Cargo.lock`.
227
-
3. Run `cargo xtask changelog` to add a new entry to the changelog.
228
-
1. This will add a list of all changes at the top. You will need to move those into the appropriate categories. Most changes that are generally not relevant to a user should be removed. Rewrite the descriptions so that a user can reasonably figure out what it means.
229
-
4. Commit the changes, and open a PR.
224
+
1. Create a PR that bumps the version and updates the changelog:
225
+
1.`git fetch upstream`
226
+
2.`git checkout -B bump-version upstream/master`
227
+
3.`cargo xtask bump <BUMP>`
228
+
- This will update the version of all the crates.
229
+
-`cargo set-version` must first be installed with `cargo install cargo-edit`.
230
+
- Replace `<BUMP>` with the kind of bump (patch, alpha, etc.)
231
+
4.`cargo xtask changelog`
232
+
- This will update `CHANGELOG.md` to add a list of all changes at the top. You will need to move those into the appropriate categories. Most changes that are generally not relevant to a user should be removed. Rewrite the descriptions so that a user can reasonably figure out what it means.
233
+
5.`git add --update .`
234
+
6.`git commit`
235
+
7.`git push`
230
236
2. After the PR has been merged, create a release in GitHub. This can either be done in the GitHub web UI, or on the command-line:
0 commit comments