Skip to content

feat: add release process to docs #358

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

Merged
jferrazbr merged 1 commit into from
Jan 28, 2026
Merged

feat: add release process to docs #358

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
30 changes: 30 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,3 +26,33 @@ can make and distribute their own plugin for any virtualization technology or
cloud provider. To browse the list of known Rancher Machine plugins, please [see
this document in our
docs repo](https://github.com/docker/docker.github.io/blob/master/machine/AVAILABLE_DRIVER_PLUGINS.md).

## Releasing a New Version

- **Prerequisite:**

- Ensure all release changes are already merged into the `master` branch before creating a tag. This process creates the tag from the latest `master` commit.

- **Prepare `master` and remote:**

- Choose your release remote (replace `<remote>`):

- `git fetch <remote> --tags`
- `git checkout master`
- `git pull --ff-only <remote> master`

- **Verify the latest tag (locally):**

- `git describe --tags --abbrev=0`

- **Create tag (from latest `master`):**

- `git tag v0.15.0-rancher<NEW-VERSION>`

- **Push the tag to your remote:**

- Push single tag: `git push <remote> v0.15.0-rancher<NEW-VERSION>`

- **Verify the tag is on the remote:**

- `git ls-remote --tags <remote> | grep v0.15.0-rancher<NEW-VERSION>`
Loading