Release v1.2.0 - #25
Merged
Merged
Conversation
Version bump across the full footprint: VERSION, __version__ in
policy_tool.py + health_check.py, the ${VERSION:-1.2.0} standalone fallback
in all 10 entrypoints + package.sh + validation-e2e.sh, and the README (en+zh)
version badges. CHANGELOG: the 19 Unreleased entries move to [1.2.0] -
2026-07-17 (Unreleased is back to empty for the next cycle); compare/tag
links updated.
Release-Checklist gates (all run on this tree):
- release-metadata 14/14 (version consistency + changelog section extract)
- bash -n + shellcheck -x on all 14 listed scripts; ruff; mypy: clean
- 454 unit tests OK; coverage TOTAL 77% (floor 70); README parity OK
- smoke-test PASS (CI-equivalent fake tailscale: status exits non-zero)
- bootstrap --dry-run --domain-pack common: exit 0, privileged commands
printed, no Advanced Mode prompt without credentials
- docs links OK; package.sh --check PASS (1.2.0 tar.gz/zip/SHA256SUMS built
and verified)
- Checklist item 7 (real-credential plan preview) SKIPPED: no
TAILSCALE_API_KEY/OAuth in env; plan/apply-plan covered by mocked tests
- Checklist item 8 run informationally on this real client host (exit 1 is
this host's genuine routing state, 37 checks emitted, schema 1)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The release bump left the Roadmap saying 'direction beyond v1.1.1' with the completed work still titled 'Now - v1.2 candidates' - a v1.2.0 tag would ship stale planning status (GPT-5.6-sol release-review F1, validated; class-swept: no other stale current-version reference in docs). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
Version bump + CHANGELOG cut for v1.2.0 (the whole merged v1.2 candidate list: broad-CDN warn-list, advisory IPv6 route check, install.sh attestation verify, OpenRC examples, policy_tool apply removal tombstone, macOS CI, Dependabot, coverage 70, bilingual README parity, plus the post-merge-audit hardenings).
Full Release-Checklist gate results are in the commit message; item 7 (real-credential plan preview) is disclosed as skipped (no credential in this environment; mocked tests cover the path).
After merge: tag v1.2.0 -> release.yml builds tar.gz/zip/SHA256SUMS + SLSA v1 attestation (first real exercise of actions/attest v4.1.1 — the PR #22 watch item) -> post-release verification incl. the exact gh attestation verify the installer runs, and an end-to-end install.sh run against the published release.
🤖 Generated with Claude Code