-
Notifications
You must be signed in to change notification settings - Fork 350
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
Reorganize project to have a single Go module #4690
Conversation
🐫 Thank you for contributing! Code Coverage Report |
1 similar comment
🐫 Thank you for contributing! Code Coverage 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.
Check also the usage of make set-module-version
which is performed during the release processes.
d3916a0
to
f9c3fab
Compare
🐫 Thank you for contributing! Code Coverage Report |
@squakez @christophd can you make a final review ? |
@squakez should be out this week. @christophd can you take a look? |
Once we merge it, there should be a Camel K release, to publish the Camel K 2.x Go modules to go.dev repo. |
I can release if needed |
Should this be 2.1.0 or 2.0.1? If 2.0.1, do we need to backport this change? It seems a breaking change. |
I will backport to the 2.0 release branch and a 2.0.1 release can be done. |
Fix #4686 and #4683
Release Note