Tag first minor release with .0 patch version #86
Conversation
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
The first kernel release of a minor version like 6.16 doesn't include a patch version. It therefore only gets the 6.16 tag. Subsequent versions like 6.16.1 get both a 6.16 and a 6.16.1 tag. This means that later patch releases overwrite the only tag for the first minor release. It is not possible to refer to that version therefore. Tag the first minor release with a .0 patch version so that 6.16.0 stays around. Signed-off-by: Lorenz Bauer <[email protected]>
lmb
force-pushed
the
tag-0-patch-versions
branch
from
92be116 to
cea9a7f
Compare
ti-mo
approved these changes
Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
The first kernel release of a minor version like 6.16 doesn't include a patch version. It therefore only gets the 6.16 tag. Subsequent versions like 6.16.1 get both a 6.16 and a 6.16.1 tag.
This means that later patch releases overwrite the only tag for the first minor release. It is not possible to refer to that version therefore.
Tag the first minor release with a .0 patch version so that 6.16.0 stays around.