Skip to content
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

Release: 0.41.0-rc1 #8106

Closed
wants to merge 1 commit into from
Closed

Release: 0.41.0-rc1 #8106

Show file tree
Hide file tree
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 docs/contributing/contributing-releases/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,7 +46,7 @@ Follow the steps below to create an RC release.

```bash
git checkout main
git checkout -b <USERNAME>/<BRANCHNAME>
git checkout -b release/<MAJOR.MINOR>
Copy link
Contributor

@sk593 sk593 Dec 5, 2024 •
edited
Loading

Choose a reason for hiding this comment

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

The release branch gets created as part of the process so we don't want to update this to the release branch:

radius/.github/scripts/release-create-tag-and-branch.sh

Line 49 in 03254be

echo "Creating release branch ${RELEASE_BRANCH_NAME}..."

Copy link
Contributor

Choose a reason for hiding this comment

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

We may also want to reopen the PR under a different branch name. Since this is the name of the release branch that gets created as part of the release process, we may be adding unintentional commits to the release branch

Copy link
Contributor Author

Choose a reason for hiding this comment

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

OK thank you - I will recreate the PR with a different branch name and delete this one.

```

1. In your local branch, update the `versions.yaml` file to to reflect the new release candidate version that we would like to release. The `versions.yaml` file is a declarative version tracking file that the Radius community maintains ([Example](https://github.com/radius-project/radius/pull/6077/files)).
Expand Down
2 changes: 2 additions & 0 deletions versions.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,6 @@
supported:
- channel: '0.41'
version: 'v0.41.0-rc1'
- channel: '0.40'
version: 'v0.40.0'
deprecated:
Expand Down
Loading