Release v0.2.0 - #157
Merged
Merged
Conversation
Bump version to 0.2.0 and add the CHANGELOG entry. Minor rather than patch: three shipped defaults changed in ways that will stop a deployment relying on the old behavior (security_mode strict, server_host loopback, per-job-type uv cache), and the default isolation posture now actually starts a container and actually enforces. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019Uz49FL6rMUyTofC4bnV2k
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.
Bump version to 0.2.0 and add the CHANGELOG entry for the 28 commits since v0.1.5.
Minor, not patch. Three shipped defaults changed in ways that will stop a deployment relying on the old behavior:
security_modedefaults tostrict(fix(defaults): fail closed on the four remaining pre-audit gaps #156), so a host without gVisor refuses to run instead of silently falling back to runc.server_hostdefaults to127.0.0.1, and a non-loopback bind withapi_auth_enabled: falseis refused at startup (fix(defaults): fail closed on the four remaining pre-audit gaps #156).The other headline is #153: the default posture (
enable_seccomp+enable_cap_restrictions) could not start a container and CI had both switched off, so the shipped default was the one configuration nothing exercised. It now works, enforces, and is what CI runs.Merging this does not publish. Pushing the
v0.2.0tag afterwards triggers the release workflow (GHCR images, PyPI via trusted publishing, GitHub Release from this CHANGELOG section).Release-notes extraction dry run against the workflow's awk produces the full 0.2.0 section (73 lines).