Skip to content

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

Closed
Rohan5commit wants to merge 1 commit intorust-lang:mainfrom
Rohan5commit:docs/release-process-marker-20260428
Closed

docs: fix the release marker label in the release process guide#4838
Rohan5commit wants to merge 1 commit intorust-lang:mainfrom
Rohan5commit:docs/release-process-marker-20260428

Conversation

@Rohan5commit
Copy link
Copy Markdown

Summary

  • fix a broken release marker in the release process guide list heading

Related issue

  • N/A (trivial docs-only fix)

Guideline alignment

  • no CONTRIBUTING guide or PR template was present in the repo root scan, so I kept this to a single-file docs-only fix on main

Validation

  • not run (docs-only change)

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

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

@ChrisDenton
Copy link
Copy Markdown
Member

Thanks but I'm closing for the above reason. I think it's clear enough for a guide aimed at the maintainers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants