Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

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

Implement Proper Tagging of Releases to Align with Update Channels #7643

Closed
contributorr opened this issue Jan 28, 2025 · 1 comment
Closed

Comments

@contributorr
Copy link

Is your feature request related to a problem? Please describe.

Currently, the GitHub release v1.31.3+rke2r1 is tagged as "latest." However, the "latest" stable release according to the RKE2 update channels is v1.31.4+rke2r1 (which is newer than the GitHub "latest" tag). Additionally, the "latest" release for the latest channel on the same page is v1.32.0+rke2r1.

This creates some confusion regarding which release should be considered the true "latest" version.

Describe the solution you'd like

Preferred: The "latest" tag on GitHub matches the "latest" release from the stable channel on the update channels page.
Alternatively, the "latest" tag on GitHub points to the version in the latest channel, and a custom "stable" tag is introduced on GitHub to represent the stable release (matching the stable channel on the update channels page).

Describe alternatives you've considered

Keep the current setup, but provide clearer documentation or guidelines on what "latest" on GitHub refers to.

Additional context

It would be helpful for users to have consistency between GitHub tags and the releases listed on the update channels page. This will prevent confusion and help users identify the correct version for their needs.

@dereknola
Copy link
Member

dereknola commented Jan 28, 2025

The latest tag for GitHub is now manually assigned, this is a change on GH's end, and makes our lives all a little more difficult, because each time we have to manually change the latest when producing new releases. Sometimes we forget and the latest tag stays on an older version.

The "latest stable" as you put it, is correct. The stable channel typically tracks behind 1 minor from latest. v1.31.4 is the correct value right now for this channel.

We generally expect RKE2 users to only need to go to the release page and manually get artifacts for the Airgap Scenario. We expect the vast majority of users to simply use the RKE2 Install Script or the Automated Upgrade System when installing new versions of RKE2. The channels page is properly up to date and maintained on our end, that is a greater source of truth.

@rancher rancher locked and limited conversation to collaborators Jan 28, 2025
@brandond brandond converted this issue into discussion #7644 Jan 28, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants