π security(deps): pin nanoid to 3.3.18 across all workspaces - #673
Conversation
β¦6-67213/67214) - nanoid 3.3.16 (root, app, apps/demo, apps/web, ui β transitive via postcss) was vulnerable to GHSA-2v37-7h3g-55p8 (CVE-2026-67213), fixed in 3.3.17 - nanoid 3.3.12 (e2e β transitive via artillery) was vulnerable to both GHSA-2v37-7h3g-55p8 and GHSA-28wg-ghj8-5hjv (CVE-2026-67214, fixed in 3.3.16) - Added `nanoid: 3.3.18` overrides to all six workspace package.json files, following the existing js-yaml security-pin pattern, and regenerated the corresponding lockfiles
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. π βΉοΈ Recent review infoβοΈ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: β Files ignored due to path filters (7)
π Files selected for processing (6)
π WalkthroughWalkthroughAdded a π₯ Pre-merge checks | β 2β Passed checks (2 passed)
β¨ Finishing Touchesπ§ͺ Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
biggest-littlest
left a comment
There was a problem hiding this comment.
Dependency pin only, follows the existing overrides security-pin pattern, gate and CI green.
17-file identity roll-forward from rc.12 to rc.13, dated 2026-08-08. - CHANGELOG: new `[1.6.0-rc.13]` section from Unreleased content β #670 digest re-anchoring, #672 self-hosted Star History, #673 nanoid pin, #682 node 24.19.0 + trivy 0.73.0 base-image bumps, #683 icon-bundle alias resolution β plus compare-link rotation - README: version badge + rc.13 highlights block - Demo mocks, site config/content, docs API pages, quickstart, updates highlights, identity-test constants, changelog-link pairs Guarded by `scripts/release-identity.test.mjs` (4/4) and the web scripts suite (56/56). Once merged: devβmain wholesale-tree sync, then dispatch `release-cut.yml` for `v1.6.0-rc.13`. GA candidate clock restarts β earliest GA β Aug 16. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Changelog π§ **Changed** - Advanced the release identity from `1.6.0-rc.12` to `1.6.0-rc.13`, dated August 8, 2026. - Updated README, demo mocks, site configuration, roadmap content, API examples, quickstart, and update highlights. - Updated changelog comparison links and release identity test constants. - Added release notes for digest re-anchoring, self-hosted Star History, `nanoid` pins, Node 24.19.0 and Trivy 0.73.0 base images, and icon-bundle alias resolution. π **Security** - Documented workspace-wide `nanoid` security pinning. - Documented base-image CVE remediation. ## Concerns - Sync the `dev` tree to `main` after merge. - Dispatch `release-cut.yml` for `v1.6.0-rc.13`. - Confirm the expected GA date remains approximately August 16. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Wholesale-tree sync ahead of the v1.6.0-rc.13 cut (same pattern as #667). The single commit carries the exact tree of `dev/v1.6` at b98808e onto `main` β after merge, `git diff --quiet origin/main origin/dev/v1.6` holds. Content on dev since rc.12: - #669/#670 β release-cut digest re-anchoring - #672 β self-hosted Star History chart - #673 β NAS acceptance follow-ups - #681 β v1.7 dependency ordering (forward-ported) - #682 β CVE base-image bumps + digest-pinned Node base guard test - #683 β icon-bundle alias resolution (fixes blank Audit/registry icons shipped in rc.12) - #684 β rc.13 identity roll-forward (17 files, CHANGELOG, README) <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Changelog - β¨ Added repository-aware Docker digest selection and multi-anchor comparison. - β¨ Added self-hosted, theme-aware Star History SVG API with pagination, caching, deadlines, and fallback rendering. - β¨ Added icon alias resolution and bundle coverage tests. - β¨ Added required icon bundle entries and updated icon mappings. - π§ Updated Node and Trivy image digests. - π Pinned `nanoid` to `3.3.18` across workspaces. - π Added a digest-pinned Node 24 Alpine base-image guard test. - π§ Updated `js-yaml` override to `3.15.1`. - π§ Updated release documentation, examples, mocks, badges, and tests to `1.6.0-rc.13`. - π§ Removed the external Star History CSP allowlist and embed. ## Concerns - Verify the Star History route stays within GitHub API rate limits under concurrent requests. - Verify cache headers do not serve incomplete or repository-specific fallback responses incorrectly. - Verify Docker digest re-anchoring preserves legacy behavior for stored containers without `repoDigests`. - Verify icon aliases with rotation or flipping have acceptable fallback behavior. - Run the Docker, Star History, icon-bundle, release-identity, and workspace dependency tests. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Summary
A new advisory pair against transitive
nanoidstarted failing the qlty security gate on every push:Pins
nanoid@3.3.18(satisfies both fixed ranges) via the existingoverridessecurity-pin pattern in all six workspacepackage.jsonfiles, following the js-yaml precedent in e2e. Lockfiles regenerated with--package-lock-only --ignore-scripts.Testing
qlty check --no-progress --allβ zero nanoid findingsnpm run buildclean in app/ and ui/Changelog
nanoiddependencies to3.3.18in all six workspacepackage.jsonfiles.--package-lock-only --ignore-scripts.3.3.16and3.3.12frompostcssandartillery.Validation
qltysecurity check passed.app/andui/builds passed.Concerns
nanoidto3.3.18.