Repository navigation
Release 0.0.1beta.13 - #104
Merged
Merged
Conversation
Dates the Unreleased section and bumps version.Version, which both the Makefile and GoReleaser inject but which is what a plain `go build`/`go install` reports. Two entries were missing and are written now rather than left out of the record: the containerd shim-name matching (`--runtime runc` refused on hosts that run runc) shipped with no entry at all, and the writability warning's printed remedy — which could widen a chgrp to a whole project and then skip the chmod via `&&` — was a user-facing correction to advice people act on. The headline of this release is that a flag could widen what `--profile prod` guarantees: `--publish`, `--user`, `--memory 0`, `--cpus 0` and `--no-hardening` were applied after the profile was checked, so prod's own promise about publishing was not enforced. That is present in 0.0.1beta.12.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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.
15 commits since
0.0.1beta.12, and one of them is why this should not wait.--profile proddid not enforce its own promise about publishing. Theprofile is asserted against the resolved configuration, but
--publish,--user,--memory,--cpusand--no-hardeningarrive as run options andare applied over that configuration afterwards. So on the released binary:
succeeds, publishes the container on every interface, and has the entrypoint
open a matching hole in the default-deny INPUT chain — which is exactly what
prod's own message says cannot happen. Fixed in #103, checked where every caller
converges so
fleetand the Studio API get the same answer.Also in: the gVisor iptables backend (#101), containerd shim-name matching
(#98),
--network allowlistfinally able to rescue a prod run (#103), thewritability warning's remedy corrected (#99), and the Linux permissions runbook
(#100).
What this PR does
Dates
Unreleasedas0.0.1beta.13 — 2026-08-09and bumpsversion.Version—which the Makefile and GoReleaser both inject, so the constant is what a plain
go build/go installreports.It also adds two entries that were missing. #98 shipped with none at all
despite being user-facing (
--runtime runcrefused on a host that runs runc),and #99 changed advice people act on — a
chgrpwidened to a whole project andchained with
&&, so one file owned by someone else stopped thechmodfromrunning. Both are in the record now rather than left out of it.
Tagging
0.0.1beta.13after this merges is what publishes.