[codex] Harden Linux release apt installs#393
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
2 participants
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 it does
Hardens Linux toolchain installation in
Release: verifyandRelease: publish.The Linux release jobs now:
http://ports.ubuntu.com/ubuntu-portstohttps://ports.ubuntu.com/ubuntu-portswhen that source exists.apt-get updateandapt-get installwith retries and explicit HTTP/HTTPS timeouts.Rationale
v0.1.50publish failed twice before build on theubuntu-24.04-armrunner because apt could not fetch packages fromhttp://ports.ubuntu.com:This is release infrastructure flakiness, not a ForkPress build failure, but it blocks the release assembly job.
Implementation
Updates only
.github/workflows/release-publish.ymland.github/workflows/release-verify.yml. The release artifacts and build commands are unchanged.Testing instructions
This is verified by the release workflow itself. After merge, rerun:
gh workflow run "Release: publish" \ --repo Automattic/forkpress \ --ref trunk \ -f release_ref=a367e3d0d4dc517107e1d0aba0b7482dafaae690