Release 0.1.17 — web-ui XSS hardening consistency#128
Merged
Conversation
Re-parented onto main tip; tree identical to dev. 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.
Release 0.1.17
Single reviewed hardening item since 0.1.16.
escAttr()/data-*sweep across the remaining server/catalog-constrained attribute + inline-JS interpolation sites — completes the #121 attribute-XSS hardening class (defense-in-depth; not exploitable today). Adversarial tests revert-proven. Also baked the "hardening PRs must prove the failure they close + docs must be truthful" lesson into.agents/knowledge/pipeline-insights.md.Plus
chore(version): VERSION 0.1.16 → 0.1.17.Gate
0.1.17(unprefixed).🤖 Generated with Claude Code