Repository navigation
ci: Go 1.26.10; the escape job runs without krun - #58
Merged
chxmxii merged 1 commit intoOct 29, 2026
Merged
Conversation
govulncheck has failed on main since 2026-10-23: GO-2026-6809 in crypto/x509, reachable from box serve, is fixed in Go 1.26.10, and go.mod pinned 1.26.9, which CI and releases build with. escape.yml symlinked krun to crun until chxperiments#56 made box stop needing krun for firecracker. chxperiments#56 has landed, so the step now fails if krun is on PATH instead, and the job stands for a firecracker-only host.
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
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.
Two small follow-ups to #55–#57.
Go 1.26.10: main's CI is red
vulncheckhas failed onmainsince the merges on 2026-10-23. GO-2026-6809 incrypto/x509, reachable frombox serve, was published after those PRs ran and is fixed in Go 1.26.10.go.modpinnedgo 1.26.9, which CI and releases build with, so every PR failsvulncheckuntil this lands. Tests, build and fuzzing were passing all along.escape.yml: no krun
#57 symlinked
kruntocrunbecause, until #56,box upneeded krun on PATH whatever the backend. #56 has landed, so that step is gone. The job now fails ifkrunis on PATH, which makes it stand for a firecracker-only host: the case #56 fixed.Checked on the fork
escape.ymlas changed here, from a copy of the branch that differs only in adding that branch to the push trigger: strict no escapes, standard no escapes (one expected warning: the VMM runs as your own UID), with krun absent. https://github.com/KoLDXr00T/bluebox/actions/runs/40180600235govulncheckreports no vulnerabilities;go test -race ./...,go vetandgofmtall pass.