fix(ci): run runtime verifier with apt privileges#12
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
Run the release-only GStreamer runtime replacement verifier with the root privileges required by its apt operations.
Why
The first
1.5.5+ceralive.1release build produced valid arm64 and amd64 packages, but the amd64 verifier exited before package installation because the unprivileged GitHub runner could not lock the apt cache.How to verify
actionlint .github/workflows/publish-release.ymlPublish CeraLive SRT Runtimewith1.5.5+ceralive.1; both packages and the amd64 GStreamer replacement check must pass before publish.Risks
The step runs as the standard passwordless GitHub Actions sudo context. Its scope is limited to the existing verifier, which already installs/removes packages in an ephemeral runner.