Skip to content

docs: fix the release marker label in the release process guide #4838

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

Closed
Rohan5commit wants to merge 1 commit into from
+1 −1
Closed

docs: fix the release marker label in the release process guide #4838

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
2 changes: 1 addition & 1 deletion doc/dev-guide/src/release-process.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -98,7 +98,7 @@ and determine which `$BRANCH` you should be working on:

Producing the final release artifacts is a bit involved because of the way
rustup is distributed. Below is a list of things to be done in order to cut a
new [b]eta release or an official [r]elease:
new [b]eta release or an official release [r]:
Copy link
Copy Markdown
Member

@ChrisDenton ChrisDenton Apr 28, 2026 •
edited by rustbot
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The original looks right to me. It's consistent with the "[b]eta" before it and is used as a key in steps below.

View changes since the review


1. [b/r] Make sure that the desired version number for the new release
`$VER_NUM` already exists in `$BRANCH`'s `Cargo.toml` file. Then in a new PR
Expand Down
Loading