Seal Chromium runtime libraries in the system runner image #7

Merged
noel merged 1 commit from fix/seal-chromium-runtime into main 2026-08-13 21:44:21 +00:00
Owner

Why

Forgejo PR #1735 proved the sealed Chromium artifact could not start in the hosted runner image because ALSA, NSPR, and NSS runtime libraries were absent.

What

  • add four exact Ubuntu Noble package payloads to the sealed-input contract
  • verify SHA-256, Debian package name, version, and architecture before installation
  • install and assert the five required shared libraries with networking disabled

Verification

  • ./test-system-hz-hermetic.sh
  • git diff --check
  • all four snapshot payload SHA-256 values verified locally
  • all four package identities, versions, and architectures verified inside the current Ubuntu runner image with --network none
Why Forgejo PR #1735 proved the sealed Chromium artifact could not start in the hosted runner image because ALSA, NSPR, and NSS runtime libraries were absent. What - add four exact Ubuntu Noble package payloads to the sealed-input contract - verify SHA-256, Debian package name, version, and architecture before installation - install and assert the five required shared libraries with networking disabled Verification - ./test-system-hz-hermetic.sh - git diff --check - all four snapshot payload SHA-256 values verified locally - all four package identities, versions, and architectures verified inside the current Ubuntu runner image with --network none
noel merged commit c974357d4b into main 2026-08-13 21:44:21 +00:00
noel deleted branch fix/seal-chromium-runtime 2026-08-13 21:44:21 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
noel/act-node-docker!7
No description provided.