-
Notifications
You must be signed in to change notification settings - Fork 516
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
Create releases for go-control-plane (0.13.4) and envoy API (1.32.3) #1079
Conversation
@@ -1,11 +1,11 @@ | |||
module-sets: | |||
go-control-plane: | |||
version: v0.13.2 | |||
version: v0.13.4 |
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.
Why not 0.13.3 ?
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.
0.13.3 was already created in the old model for the go.mod issue (technicality to ensure we can release 13.4 without forcing go 1.22.8 on dependents)
https://github.com/envoyproxy/go-control-plane/releases/tag/v0.13.3
The build is failing, any idea ? |
I think this is a dead end right now. I can cut the tags from this branch, as the rebase and merge should not alter the commits (if I rebase before as the envoy sync got fixed and just altered main) |
Signed-off-by: Valerian Roche <[email protected]>
Signed-off-by: Valerian Roche <[email protected]>
82b67b2
to
e7169a6
Compare
Just rebased on main. Will tag from here once approved |
Signed-off-by: Valerian Roche <[email protected]>
e7169a6
to
46e0318
Compare
Pushed the commits and tags on main. Hopefully should recover the issues |
PR directly merged on |
This PR creates new releases that will hopefully address #1074
This PR will NOT build as is, given the tags not being pushed yet