Release v1.1.1: site hardening + docs - #9
Merged
Merged
Conversation
Patch release. spec/levels.json content is byte-identical — same six levels, same definitions, same decision tree — so no published declaration is affected; only the version string and the site/docs move. - Version 1.1.0 → 1.1.1 (package.json, spec/levels.json, CITATION.cff, 22 manifestos); release dates → 2026-07-22 (CHANGELOG, CITATION date-released, spec updated). - CHANGELOG: 1.1.1 entry — EN-only page canonicalisation, strict CSP + security headers, threat model + FAQ docs. - README: link the new docs/FAQ.md and docs/THREAT-MODEL.md so they aren't orphaned. Verified: npm run verify passes; feed.xml parses the 1.1.1 entry. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
Patch release — the scale itself is unchanged.
spec/levels.jsonlevel content is byte-identical (same six levels, same definitions, same decision tree), so no declaration already published is affected. Only the version string, the release dates, the CHANGELOG, the site hardening (already merged in #7) and the docs (already merged in #8) are captured here.1.1.0→1.1.1acrosspackage.json,spec/levels.json,CITATION.cff, and all 22 manifestos; dates → 2026-07-22.1.1.1entry (EN-only page canonicalisation, strict CSP +X-Frame-Options/Permissions-Policy, threat model + FAQ).docs/FAQ.mdanddocs/THREAT-MODEL.md.Verified:
npm run verifypasses;feed.xmlparses the new entry.After merge,
v1.1.1is tagged (signed) to publish the GitHub Release.🤖 Generated with Claude Code