Ship again
gstack /cso runtimes can ship again without a paid requalification
qualified setSTALE_RUNTIME_QUALIFICATIONreleasable
Ship againOne lineStill countsYour setup
garrytan/gstack · CHANGELOG.md · 1.91.176.0
gstack can release its qualified /cso runtime set again. Qualification had refused it as stale. The fix lets it ship without paying for a fresh qualification run.
One line
One unused line moved the fingerprint
line 1#!/usr/bin/env bunisolated shebang
The fingerprint now skips that line in both compiled helpers.
Ship againOne lineStill countsYour setup
garrytan/gstack · CHANGELOG.md · 1.91.176.0
The cause was one line. A shebang change in two compiled helpers moved the fingerprint, though that line never runs in the image. The fingerprint now ignores it.
Still counts
Every other byte still counts
Line 2 of either helper: still stale
An image Dockerfile edit: still stale
The image entrypoint shebang: still stale
Ship againOne lineStill countsYour setup
garrytan/gstack · CHANGELOG.md · 1.91.176.0
Every other byte still counts. A second-line edit to either helper is still stale. So is a Dockerfile edit, and so is a shebang change to the image entrypoint.
Your setup
The full rule is in the changelog
CHANGELOG.md1.91.176.0, Gate integrityWhich stack do you point /cso at?
Ship againOne lineStill countsYour setup
garrytan/gstack · CHANGELOG.md · 1.91.176.0
The changelog spells out the full rule. Which stack do you point /cso at?
