fix(release): build GNU artifacts against Bookworm-compatible glibc - #101
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
ubuntu-latest0.7.0-rc.2Why
The
v0.7.0-rc.1release built its GNU binary on Ubuntu 24.04, which linked against GLIBC 2.38+, then copied that binary into the Debian Bookworm runtime image, which provides glibc 2.36. The pushed amd64 image therefore failed its smoke test before the server could start.Building on Ubuntu 22.04 (glibc 2.35) keeps the standalone GNU archives and Debian Bookworm images backward-compatible without changing the production runtime base.
Impact
This unblocks publication of a Cloud-compatible engine release candidate. No engine runtime behavior changes in this PR.
Validation
actionlint .github/workflows/release.ymlbash scripts/test-review-fix-guards.shcargo metadata --locked --no-deps --format-version 1git diff --checkThe authoritative runtime validation remains the release workflow's amd64 and arm64 image smoke tests after merge and tagging.