Skip to content

chore(deps): clear astro and node-forge security alerts - #4577

Merged
thymikee merged 2 commits into
mainfrom
security/2026-11-16-deps
Nov 16, 2026
Merged

thymikee merged 2 commits into
mainfrom
security/2026-11-16-deps

Conversation

@thymikee

@thymikee thymikee commented Nov 16, 2026 •

Copy link
Copy Markdown
Member

Summary

Clears Dependabot alerts #184, #185, #186, #187, #188 and #189. None of these packages ships in the published package. 4 files touched.

All resolved versions are older than the minimumReleaseAge window.

$ pnpm why astro            # root
astro@7.4.12  (single version; via agent-device-website, @astrojs/starlight@0.42.7, @astrojs/mdx@8.1.1, astro-expressive-code@0.44.3, starlight-llms-txt@0.12.0)
$ pnpm why node-forge       # examples/test-app
node-forge@1.4.3  (single version; via @expo/cli@58.0.3, @expo/code-signing-certificates@0.0.6)

Validation

Tested SHA af40cb8.

  • pnpm --filter agent-device-website build: pass
  • pnpm --filter agent-device-website check: 0 errors, 0 warnings
  • pnpm run test:concurrency-torture: 4 pass (it failed on 821878e in CI)
  • pnpm format: no changes
  • CI covers check:affected and the remaining lanes.

🤖 Generated with Claude Code

Raise the website astro floor to ^7.4.7 (resolves 7.4.12) for
GHSA-r3h5-4585-7x3w and GHSA-mh32-jxcr-mh9f. Move the transitive
@astrojs/astro2tsx to 0.1.4, which declares its own @emnapi/runtime;
0.1.3 took the rolldown wasm binding's 2.0 beta as a peer and broke
astro check.

Raise the examples/test-app node-forge@1 override to ^1.4.3.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

github-actions Bot commented Nov 16, 2026 •

Copy link
Copy Markdown
Contributor

Size Report

Metric Base Current Diff
Installed (including dependencies) 6.30 MB 6.30 MB +22 B
Package (unpacked) 6.30 MB 6.30 MB +22 B
Package (download) 1.91 MB 1.91 MB +13 B

Startup median (7 runs, lower is better):

Scenario Base Current Diff
CLI --version 28.4 ms 26.0 ms -2.4 ms
CLI --help 50.6 ms 47.6 ms -3.1 ms

@cubic-dev-ai cubic-dev-ai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No issues found across 4 files

You’re at about 95% of the monthly reviewed-line limit. You may want to disable incremental reviews to conserve quota. Reviews will continue until that limit is exceeded. If you need help avoiding interruptions, please contact contact@cubic.dev.

View guided diff | Turn on auto-fix | Re-trigger cubic

astro 7.4.12 needs vite ^8.3.6 and yaml 2.9.1, so the lockfile kept
the repo's vite 8.3.5 / yaml 2.9.0 beside them. That gave two vitest
peer variants, and the concurrency-torture lane loaded both and failed
with "Vitest failed to access its internal state". Resolve vite to
8.3.8 and yaml to 2.9.1 within the existing ranges.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@apex-sentinel-staging

Copy link
Copy Markdown

Apex Sentinel · ✅ Approve

No open findings.

Not in the reviewers' prompt (2 files)
  • examples/test-app/pnpm-lock.yaml: generated or a lockfile, so its lines were left out
  • pnpm-lock.yaml: generated or a lockfile, so its lines were left out

Reviewed with this repository's own Sentinel configuration (189570486a11).

💬 Talking to Sentinel

In a finding's thread, reply with:

Command What it does
@apex-sentinel-staging note <context> Adds context; Sentinel re-checks the cited code
@apex-sentinel-staging pivot <why> Says the finding is wrong; Sentinel re-checks the cited code
@apex-sentinel-staging like Marks the finding as useful
@apex-sentinel-staging dislike <why> Marks it as not useful, so it is not raised again

On this conversation, comment @apex-sentinel-staging review to run a full review once again.

@thymikee

Copy link
Copy Markdown
Member Author

I found no problems in af40cb8. The astro and node-forge bumps look correct, and all 25 checks pass. There are no conflicts. The lock diff is large because of transitive astro changes. Nothing else is needed before merge.

@thymikee thymikee added the ready-for-human Valid work that needs human implementation, judgment, or maintainer merge label Nov 16, 2026
@thymikee
thymikee merged commit 03e09ae into main Nov 16, 2026
25 checks passed
@thymikee
thymikee deleted the security/2026-11-16-deps branch November 16, 2026 09:03
thymikee added a commit that referenced this pull request Nov 16, 2026
* origin/main:
  fix(alert): derive the request envelope from an alert wait window (#4581)
  fix(android): require a nonzero chunk before a recorder counts as ready (#4559)
  chore(deps): clear astro and node-forge security alerts (#4577)
  fix(ios): establish the screen origin of a full-screen private AX root (#4573)
  docs(agents): trace behavior claims during review (#4576)
  fix(mcp): trim the press plan text back under the always-loaded byte budget (#4572)
  refactor(alert): one helper owns the alert runner budget (#4563)
  feat(interaction): multi-ref press plan lowered through the ordinary press lane (#4296)
  fix(ios): use the caller's budget for alert get and type the watchdog outcome (#4540)
  feat(recovery): bound remote health and runner-busy recovery by the command's deadline (#4541)
  fix(ios): find the navigation bar back button outside the bar's subtree (#4542)
  feat(open): report device kind, model and osVersion on open and session identity (#4543)
  fix(apple): use typed screenshot timeouts and observed shutdown recovery (#4544)
  feat(device-status): report per device whether a new session can take it (#4547)
  fix(runner): type the refusals for a control the target cannot supply (#4548)
  refactor(transport): share outgoing transfer phase ownership (#4551)
  fix(remote): bound artifact preparation and upload phases (#4552)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-for-human Valid work that needs human implementation, judgment, or maintainer merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant