feat: add release process to docs#358
Merged
jferrazbr merged 1 commit intorancher:masterfrom Jan 28, 2026
Merged
Conversation
jiaqiluo
previously approved these changes
Jan 28, 2026
README.md
Outdated
|
|
||
| - **Create tag (from latest `master`):** | ||
|
|
||
| - `git tag vX.Y.Z` |
There was a problem hiding this comment.
can we include the expected tag format for reference? (e.g. v0.15.0-rancher<VERSION>)? It's a weird format, and if you don't look at existing tags someone might confuse it with typical semver. At this point I don't think we'll ever get to v0.16.0.
Author
There was a problem hiding this comment.
Make sense, I will change the tag format
jferrazbr
force-pushed
the
docs/add_release_process
branch
from
cee78b9 to
88a7a84
Compare
HarrisonWAffel
approved these changes
Jan 28, 2026
jiaqiluo
approved these changes
Jan 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue:
N/A (no GitHub issue for this PR).
Problem
Today the
rancher/machinerepo does not explain the release steps in the documentation.Solution
Add a new section to
README.mdcalled "Releasing a New Version" with a small checklist and the main git commands to:masteris up to datemasterTesting
Not applicable. This PR only updates documentation.