Skip to content

build(deps): закрыть advisory nanoid<3.3.18 подъёмом override до ^3.3.18 - #279

Merged
lemone112 merged 1 commit into
mainfrom
fix/nanoid-audit-3318
Aug 18, 2026
Merged

build(deps): закрыть advisory nanoid<3.3.18 подъёмом override до ^3.3.18#279
lemone112 merged 1 commit into
mainfrom
fix/nanoid-audit-3318

Conversation

@lemone112

Copy link
Copy Markdown
Contributor

Что

Advisory-класс nanoid вернулся третий раз (#255#272 → текущий): GHSA сдвинул границу уязвимых версий до <3.3.18, override ^3.3.17 из #272 стал недостаточен. main латентно красный по pnpm audit --audit-level moderate — это валит CI любого свежего lockfile (доказательство: dependabot PR #278, run 31987225212, шаг audit).

Доказательства

  • RED: pnpm audit --audit-level moderate на main → HIGH nanoid <3.3.18 (пути vite>postcss>nanoid, vitest>@vitest/mocker>vite>postcss>nanoid).
  • GREEN: после override nanoid@<3.3.18: ^3.3.18 и пересборки lockfile → No known vulnerabilities found.
  • Защита класса: audit-шаг уже стоит первым в verify-цепи CI — регресс не пройдёт молча.

Контекст плана

Узел TRUST-01 трека plans/lab-motion-production (agents-config PR #12): разблокирует релизный путь 0.4 и dependabot-очередь (#275#278).

Rollback

Revert-PR этого squash-коммита; audit ожидаемо вернётся в красное известное состояние.

RED: pnpm audit --audit-level moderate на main падает HIGH (nanoid <3.3.18,
пути через vite>postcss и vitest) — CI run 31987225212 (PR #278).
GREEN: после override и пересборки lockfile audit чист локально.
Гейт INV-18 (audit в verify-цепи) не даёт классу вернуться молча.
@coderabbitai

coderabbitai Bot commented Aug 18, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 58 minutes

Limit details: You’ve used all 1 included review currently available under your plan. You completed 105 included PR reviews in the past 7 days; at that activity level, included reviews refill at 1 review per hour.

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 85d3adcc-774b-427d-b89c-f3e0e55b037b

📥 Commits

Reviewing files that changed from the base of the PR and between 596179d and 103bbf6.

⛔ Files ignored due to path filters (1)
  • pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml
📒 Files selected for processing (1)
  • pnpm-workspace.yaml

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant