Repository navigation
docs(release): M14.7 — Security guide, decisions, CHANGELOG 0.18.0, version bump - #218
Merged
Merged
Conversation
…0 and the version bump docs/guide/13-security.md: the security layer in one page — stack, advisories (what leaves the machine, the incident, the agent's context, Upgrade), news and its sources with the format check, the two rules, the CLI, the config. The Observatory guide points to it. docs/16-security.md flips to living with an addendum on what differs in what shipped (declared-runtime keywords after the first real run, the advisory_packages table, the /v1/context double registration the M14.8 test found, the scriptable format check, no schema bump, the measured numbers). OQ-31, OQ-35 and OQ-36 decided; the features catalog gains the Secure group; the roadmap's M14 header and M14.7 row flip; the public ROADMAP's Phase 14 is done; the index row and the interface heading move on; CLAUDE.md's status says what M14 is. CHANGELOG 0.18.0 written first, then `bun tools/version.ts 0.18.0` bumped every version field and drafted docs/marketing/v0.18.0-x.md, polished in the plain first-person voice. Tagging v0.18.0, pushing the tag and `bun run site:deploy` are the release ritual's remaining steps. Verified: docs:check (17 files) · site:build renders 13 guide + 16 design docs at v0.18.0 · typecheck · lint · test (1084 pass) · smoke · no company names in the diff. Co-Authored-By: Claude <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
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.
The last M14 task. Docs and release preparation only — no behaviour changes beyond the version fields.
What it adds
docs/guide/13-security.md: the security layer in one page — stack, advisories (what leaves the machine, the incident, the agent's context, Upgrade), news and its sources with the format check, the two rules, the CLI, the config.docs/16-security.mdflips to living with an addendum on what differs in what shipped; OQ-31, OQ-35 and OQ-36 decided; the features catalog's Secure group; the roadmap's M14 header ✅; the public ROADMAP's Phase 14; CLAUDE.md's status.CHANGELOG.md0.18.0 — written first, thenbun tools/version.ts 0.18.0bumped every version field (root, npm bundle, Tauri, daemon) and drafteddocs/marketing/v0.18.0-x.md, polished.Left for the release ritual after merge (outward-facing, so not done here):
git tag v0.18.0,git push --tags(that publishes the npm package and the desktop app throughrelease.yml), thenbun run site:deployand a check ofgetswarm.vercel.app/changelog. The X post is indocs/marketing/v0.18.0-x.mdmarked draft.Verification: docs:check (17 files) · site:build renders 13 guide + 16 design docs at v0.18.0 · typecheck · lint · test (1084 pass) · smoke · the diff carries no company names.
🤖 Generated with Claude Code