docs: update the upgrade talos version make target#638
Open
Iheanacho-ai wants to merge 1 commit into
Open
Conversation
Iheanacho-ai
force-pushed
the
make-targizzy
branch
2 times, most recently
from
a166f6f to
524e136
Compare
Iheanacho-ai
force-pushed
the
make-targizzy
branch
from
524e136 to
678d535
Compare
Signed-off-by: Amarachi Iheanacho <amarachi.iheanacho@siderolabs.com>
Iheanacho-ai
force-pushed
the
make-targizzy
branch
from
678d535 to
f5ea51f
Compare
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.
What
Makes make upgrade-talos-version driven by an explicit tag instead of guessing the next version.
Why
The old target guessed the version by bumping the minor, which overshot whenever the pins were already advanced during an alpha. It also never regenerated reference docs and didn't validate input.
Changes