-
Notifications
You must be signed in to change notification settings - Fork 334
build: prepare for 1.6.0 dev #4054
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zalimeni just a heads up that I noticed this morning that the 1.4.x versions of
consul-cnifrom 1.4.2 when this was introduced are all showing1.5.0-devrather than the correct version. Not sure if that's something that should be addressed in this PR or is a missing step in the release checklist.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tgross thanks for the heads up - I'm guessing a step was accidentally skipped when creating those patch releases. Having a look shortly, but it shouldn't impact this PR as
mainis ahead of those.❓ just TBC, are you referring to released artifacts, or local builds from
release/1.4.x? If the former, we may want to add a note to the changelog(s) that the version is incorrectly reported (I thought we had checks for this in CRT but perhaps there's a gap somewhere).There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The ones downloaded from https://releases.hashicorp.com/consul-cni, unfortunately:
I can file an issue for this somewhere if you'd like, but I noticed this PR while looking for an existing report.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @tgross - appreciate you noticing and reporting. If you want to drop a message in the Consul team Slack for 👀 and tag me, that would be great, and we can decide how to follow up from there 🙏🏻
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.4.3 was still released as 1.5.0-dev:
@zalimeni have we validated this is fixed for 1.6.0 ?
( @tgross 👋 miss yah! )
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@flyinprogrammer thank you for the heads up! Unfortunately this was caught just as we were releasing 1.4.3, so we weren't able to address for that release, but are hoping to have this fixed in the next set of releases.
(For posterity: the issue was that we backported some changes to the
cnisubmodule prior to1.4.2that instigated a bump to the pinnedcontrol-planesubmodule introduced recently to consume the common version string; that new SHA had 1.5.0-dev in theversion.gofile. I think the best approach to avoid this repeating in the future will be to moveconsul-k8sbinaries to theversion/VERSIONembedded file scheme thatconsuluses, or introduce areplaceforcontrol-planeincni'sgo.modto ensure we're always using the current revision'sversion.go.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@flyinprogrammer
Same!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Closing the loop: #4091 this should address the versioning issues going forward. Thanks again for the report @tgross !