chore(release): 1.1.16 — hygiene tail after the 1.1.12 → 1.1.15 series#218
Merged
Conversation
No new user-facing features. Bump cli/args.cpp --version literal and fold the post-1.1.15 build/CI/process landings into a CHANGELOG entry: - Build: -lnv for FreeBSD nvpair (#215) closed the latent crate(1) link error the lite workflow could not see. - CI: link smoke for crate(1) in lite (#215); master→main trigger fix and monthly cron (#216); cross-platform-actions v0.32.0 → v1.2.0 for the June 16 Node 24 cutover, removed superstitious VM resource overrides (#217); full workflow converted to workflow_dispatch-only after GitHub-hosted FreeBSD runners proved unfit for ci-verify (#217). lite is now the sole automated FreeBSD gate, ~3-5 min, reliably green on every push. - Docs: scripts/on-hardware-validation.sh + docs/on-hardware-validation.md consolidate the on-hardware checklists from #210..#213 (#214); docs/getpeereid-main-api-refactor.md records the design call to defer the big refactor (#215); TODO audit retires completed entries and backfills the Done list (#216). trust-model.{md,uk.md} Applies-to bumped 1.1.15 → 1.1.16. Substantive trust-model content is unchanged. Ready for tag: git tag v1.1.16 && git push origin v1.1.16 (release.yml builds the FreeBSD binaries on v* push.) https://claude.ai/code/session_01X6t6tzVypHye5bDGLxzmZK
Audit of the 1.1.16 release commit found four "current-version"
references that the earlier pass missed:
- docs/trust-model.{md,uk.md} "Reasoning about isolation on 1.1.15"
-> 1.1.16 (matches the freshly-bumped "Applies to" line at top)
- docs/on-hardware-validation.md "from main >= 1.1.15" and
"crate --version # expect 1.1.15+" -> 1.1.16
Other 1.1.15 mentions in the repo are historical landed-in markers
(e.g. // 1.1.15: create_jail's path argument, "Done (1.1.15): the
last narrow item", PR #213 (1.1.15)) and stay as-is by convention,
same as // 1.1.11: send a signal ... did when we bumped to 1.1.15.
https://claude.ai/code/session_01X6t6tzVypHye5bDGLxzmZK
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
2 participants
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.
Summary
Release-cut commit. No new user-facing features — just the version literal, the CHANGELOG entry, and the trust-model "Applies to" line. Everything material has already shipped in #214–#217.
Changes
cli/args.cpp— both--version/-Vbranches bumpedcrate 1.1.15→crate 1.1.16.CHANGELOG.md— new[1.1.16] — 2026-06-10entry, sectioned by Build / CI / Operator docs, citing the four PRs that comprise the release.docs/trust-model.{md,uk.md}—Applies to: 1.1.15→1.1.16. Substantive trust-model content (1.1.12 → 1.1.15 gate series) is unchanged.What landed since 1.1.15
scripts/on-hardware-validation.sh+docs/on-hardware-validation.mdconsolidating the on-hardware checklists from #210..#213-lnvlink fix; lite-CI link smoke forcrate(1); getpeereid + layered-images design notesmaster→main; cron weekly→monthlycross-platform-actionsv1.2.0; full FreeBSD build →workflow_dispatch-only after the SSH-flake + ci-verify-timeout investigation; lite gates every pushReady for tagging
After merge, the release flow is the existing one:
release.yml(unchanged) is triggered bypush: tags: ['v*'], buildscrate/crated/crate-snmpdon FreeBSD VMs per the supported-version matrix, and attaches the tarballs to the GitHub Release created from the tag.Test plan
cli/args.cppliteral grep'd — both branches now printcrate 1.1.16.[1.1.15], structure matches the existing release-entry shape.gmake cratewith the new literal.https://claude.ai/code/session_01X6t6tzVypHye5bDGLxzmZK
Generated by Claude Code