Skip to content

release: v0.5.2 notes and install-doc literals - #252

Open
avi-papineni wants to merge 2 commits into
mainfrom
release/notes-v0.5.2
Open

avi-papineni wants to merge 2 commits into
mainfrom
release/notes-v0.5.2

Conversation

@avi-papineni

Copy link
Copy Markdown
Contributor

The notes PR for v0.5.2, carrying out steps 1 and 2 of docs/development.md#releasing. Docs and changelog only; no code changes.

What it does

Sweep

$ git grep -n '0\.5\.1' -- README.md docs/ ':!docs/adr' ':!CHANGELOG.md'
$ echo $?
1

Nothing is left over. No remaining place names the previous release.

Release-gate check

Run the way release.yml runs it (scripts/check-release-literals.sh "${{ github.ref }}"):

$ scripts/check-release-literals.sh refs/tags/v0.5.2
README.md's quickstart checks out v0.5.2
$ scripts/check-release-literals.sh v0.5.2
README.md's quickstart checks out v0.5.2

After merge

The maintainer tags the merge commit on main (git tag -a v0.5.2 -m v0.5.2 <merge commit>, then git push origin v0.5.2). Then they check the draft's assets, title it, write its notes from this section, and publish. This PR does not tag or release.


Generated by Claude Code

The v0.5.2 notes PR, as docs/development.md#releasing steps 1 and 2
describe it.

- CHANGELOG.md: Unreleased becomes the v0.5.2 section, titled. A lead
  paragraph states the one behavior change: an entry ending in a
  separator (tcp:, tcp/, udp:, udp/, icmp:, icmp/) is refused on the
  command line and in the console, every port is written as the bare
  protocol, and scripts passing --entry tcp: must change; stored
  services and rules, documents, and REST bodies are unaffected. The
  #239 entry names icmp/ and the script change, the #218 entry names
  ADR-0016's dated amendment, and a closing line says both binaries
  replace v0.5.1 in either order: no migration, proto, or operator API
  contract change since v0.5.1.
- README.md, docs/reference/versioning-and-install.md, and
  docs/deploy/README.md name v0.5.2, the tag these docs ship in.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: Claude <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 11, 2026 •

Copy link
Copy Markdown

No ADR contradictions found (diff-anchored review).

This PR touches only CHANGELOG.md, README.md, docs/deploy/README.md, docs/reference/versioning-and-install.md, Dockerfile, and go.mod — version-literal bumps (v0.5.1 → v0.5.2, Go 1.26.10 → 1.26.11) and the changelog section for the release. It does not touch docs/adr/ or CLAUDE.md, so this is a diff-anchored review, not a full-corpus audit.

Checks performed:

  • ADR-0016 amendment claim. The new changelog entry says "ADR-0016 takes a dated amendment" for the suspend/renewal fix (agent: a renewal instant that passes during host suspend is not acted on after resume — no wall-clock renewal check at stream establishment #218). docs/adr/0016-enrollment-identity-credentials.md's ## Amendments section already carries this: "2026-11-10 (issue agent: a renewal instant that passes during host suspend is not acted on after resume — no wall-clock renewal check at stream establishment #218): a renewal point that passes while the host is suspended. Additive detail on decision 4, corrected in place ... the core decision stands." The amendment was made in a prior merge (already on main), follows the in-place-amendment convention in docs/adr/README.md (dated note, references the issue, core decision stated as standing), and the claim in this PR's changelog text is accurate.
  • "No agent-contract / operator-API-contract change" claim. Verified git log v0.5.1..HEAD -- proto/ internal/api/ and -- internal/store/migrations/ are empty: no proto, operator-API, or migration changes since v0.5.1, consistent with the changelog's closing line and with ADR-0007/ADR-0021 (proto is the agent contract; operator REST is hand-shaped HTTP over the domain layer) and the goose migration rule in CLAUDE.md.
  • icmp/ refusal claim. The changelog's amended description of policy: a separator with no ports after it (tcp:, tcp/) silently means every port #239 adds that icmp/ (not just icmp:) was previously read as bare icmp and is now refused on an empty port list. internal/policy/document.go's EntrySpecDoc splits on strings.IndexAny(s, ":/") uniformly, so icmp/ and icmp: take the same path into entryFromDoc, which rejects an empty ports list. The text matches the code.
  • Go toolchain bump (go.mod, Dockerfile). A patch bump for a disclosed net/http vulnerability (GO-2026-6859); the changelog correctly notes agents fail static when the control plane is down (ADR-0011) and that no Innerwall code changes — consistent with that ADR, and nothing here touches firewall-table handling, agent self-update, or flow shipping.
  • scripts/check-release-literals.sh referenced in the PR description already exists on main and is unchanged by this diff — no dangling reference.
  • No ORM/query-builder, polling, nftables, agent fail-open/closed, flow-aggregation, FlowStore-bypass, UI-backchannel, operator-handler-domain-logic, outbound-policy, certificate-mutable-attribute, control-plane-replica-state, unsigned-rendered-policy, or Makefile-logic changes are present — the diff is documentation and version literals only.
  • No comparisons to competing products and no origin-story references were introduced; the implementation stack (Go, the toolchain version) is named, which the rules permit.

No superseding ADR is needed or present, and none was required.

Copy link
Copy Markdown
Contributor Author

known vulnerabilities fails on this PR, and the failure does not come from this PR's change. GO-2026-6859 (net/http, fixed in Go 1.26.11) entered the vulnerability database after af42131 last passed the job, so every PR now fails it on Go 1.26.10. The release workflow runs ci.yml on the tagged commit, which means v0.5.2 cannot be tagged until the toolchain moves. That fix and its changelog entry are tracked in #253. This PR stays docs-only. Once #253 lands, this branch takes main and the v0.5.2 section gains that entry.


Generated by Claude Code

The known-vulnerabilities gate fails on Go 1.26.10: the operator surface
reads request bodies through http.MaxBytesReader, which the advisory
names. go.mod and the image's build stage move to 1.26.11; no code
changes.

Fixes #253.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Signed-off-by: Claude <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants