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

Create releases for go-control-plane (0.13.4) and envoy API (1.32.3) #1079

Closed
wants to merge 3 commits into from

Conversation

valerian-roche
Copy link
Contributor

@valerian-roche valerian-roche commented Jan 3, 2025

This PR creates new releases that will hopefully address #1074

This PR will NOT build as is, given the tags not being pushed yet

@@ -1,11 +1,11 @@
module-sets:
go-control-plane:
version: v0.13.2
version: v0.13.4
Copy link
Contributor

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 ?

Copy link
Contributor Author

@valerian-roche valerian-roche Jan 3, 2025

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

mmorel-35
mmorel-35 previously approved these changes Jan 3, 2025
@mmorel-35 mmorel-35 self-requested a review January 3, 2025 21:20
@mmorel-35
Copy link
Contributor

The build is failing, any idea ?

@valerian-roche
Copy link
Contributor Author

valerian-roche commented Jan 3, 2025

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)

@valerian-roche
Copy link
Contributor Author

Just rebased on main. Will tag from here once approved

@valerian-roche valerian-roche enabled auto-merge (rebase) January 3, 2025 21:31
@valerian-roche
Copy link
Contributor Author

Pushed the commits and tags on main. Hopefully should recover the issues

@valerian-roche
Copy link
Contributor Author

PR directly merged on main branch to handle the "chicken-and-egg" tagging situation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants