8616839cab
CHANGELOG promotion was a manual operator step that was never run, so 463 fragments for work already shipped in <=1.3.1 accumulated in .changeset/. Their notes were already hand-curated into the dated [1.2.0]/[1.3.0]/[1.3.1] CHANGELOG sections (#690 backfill, PR #694). Rendering them now would duplicate and mis-attribute shipped work. Move them to .changeset/archived/ (read non-recursively by all changeset tooling, so never rendered), keeping only the 3 genuinely-unreleased fragments at the top level. Prep for wiring `render` into the release finalize job (#690 follow-up). Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
656 B
656 B
type, pr
| type | pr |
|---|---|
| Security | 113 |
Scanner now detects malicious markdown link schemes — scanForInjection() previously passed markdown links containing javascript:, data: (non-image/font), https://user:pass@host userinfo credentials, and sensitive query-string key names (token=, api_key=, etc.) as clean. Four new rules (MD-LINK-JS-SCHEME, MD-LINK-DATA-SCHEME, MD-LINK-USERINFO, MD-LINK-TOKEN-IN-QUERY) now flag these patterns in both the scanner and the gsd-read-injection-scanner.js hook. The data: safe-list permits image and font MIME types; data:image/svg+xml is intentionally blocked because SVG can host inline scripts.