-
Notifications
You must be signed in to change notification settings - Fork 6
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
Update module version to v3 #1359
Conversation
CHANGELOG.md
Outdated
@@ -13,7 +13,8 @@ and this project's packages adheres to [Semantic Versioning](http://semver.org/s | |||
|
|||
### Changed | |||
|
|||
- CAPA only change for new releases: render release version in config instead of cluster-aws version in App resource. | |||
- **BREAKING** CAPA only change for new releases: render release version in config instead of cluster-aws version in App resource. |
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.
I have to admit I don't really understand the changelog entry. Can we explain this in more natural language? Also, which commands are affected?
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.
I have updated changelog so it's more clear.
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.
Thank you!
What does this PR do?
This PR bumps go module version to v3, due to a breaking change that has been added here #1352.
What is the effect of this change to users?
See #1352.
What does it look like?
See #1352.
Any background context you can provide?
giantswarm/roadmap#3466
Do the docs need to be updated?
Will check.
Should this change be mentioned in the release notes?
Is this a breaking change?
(Breaking changes are, for example, removal of commnds/flags or substantial changes in the meaning of a flag. If yes, please add the
breaking-change
label to the PR.)Yes.