Skip to content
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

Merged
merged 4 commits into from
Jun 27, 2024
Merged

Update module version to v3 #1359

merged 4 commits into from
Jun 27, 2024

Conversation

nprokopic
Copy link
Contributor

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?

  • CHANGELOG.md has been updated

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.

@nprokopic nprokopic added the breaking-change Used to label pull requests containing changes that break the API (commands, flags, defaults) label Jun 26, 2024
@nprokopic nprokopic requested review from a team as code owners June 26, 2024 11:15
@nprokopic
Copy link
Contributor Author

cc @ssyno if you would like to merge this first #1212 and then we can rebase this PR.

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.
Copy link
Member

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?

Copy link
Contributor Author

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.

Copy link
Member

@marians marians left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@nprokopic nprokopic merged commit a69f007 into main Jun 27, 2024
3 checks passed
@nprokopic nprokopic deleted the release-v3 branch June 27, 2024 10:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Used to label pull requests containing changes that break the API (commands, flags, defaults)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants