Skip to content

chore(website): update all node deps to latest and bump node#653

Merged
marvin-hansen merged 2 commits into
deepcausality-rs:mainfrom
marvin-hansen:main
Jun 25, 2026
Merged

chore(website): update all node deps to latest and bump node#653
marvin-hansen merged 2 commits into
deepcausality-rs:mainfrom
marvin-hansen:main

Conversation

@marvin-hansen

@marvin-hansen marvin-hansen commented Jun 25, 2026

Copy link
Copy Markdown
Member

Describe your changes

update all node deps to latest and bump node

  • web: astro 6→7, @astrojs/mdx 6→7, astro-mermaid 2.0.2→2.1.0, wrangler 4.101.0→4.104.0, pnpm 11.0.9→11.9.0
  • docs: astro 6→7, @astrojs/starlight 0.40→0.41, sharp 0.35.1→0.35.2; regenerated package-lock.json
  • node 26.3.0→26.3.1 (homebrew)

Issue ticket number and link

Code checklist before requesting a review

  • I have signed the DCO?
  • All tests are passing when running make test?
  • No errors or security vulnerabilities are reported by make check?

For details on make, please see BUILD.md

Note: The CI runs all of the above and fixing things before they hit CI speeds
up the review and merge process. Thank you.


Summary by cubic

Upgrade the website and docs to Astro 7 and bump Node to 26.3.1; also remove a redundant sharp dependency from docs. Includes updates to @astrojs/mdx, astro-mermaid, @astrojs/starlight, wrangler, and pnpm; both sites build clean.

  • Dependencies

    • web: astro 6→7, @astrojs/mdx 6→7, astro-mermaid 2.0.2→2.1.0, wrangler 4.101.0→4.104.0, pnpm 11.0.9→11.9.0
    • docs: astro 6→7, @astrojs/starlight 0.40→0.41; remove direct sharp; regenerated package-lock.json
    • workspace: allow workerd builds; exclude astro-mermaid@2.1.0 from minimumReleaseAge
    • Node: 26.3.0→26.3.1
  • Migration

    • Use Node 26.3.1+.
    • Reinstall dependencies in both apps.

Written for commit 02ebf4b. Summary will update on new commits.

Review in cubic

- web: astro 6→7, @astrojs/mdx 6→7, astro-mermaid 2.0.2→2.1.0,
  wrangler 4.101.0→4.104.0, pnpm 11.0.9→11.9.0
- docs: astro 6→7, @astrojs/starlight 0.40→0.41, sharp 0.35.1→0.35.2;
  regenerated package-lock.json
- node 26.3.0→26.3.1 (homebrew)

Both sites build clean.

Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
@marvin-hansen marvin-hansen self-assigned this Jun 25, 2026
@socket-security

socket-security Bot commented Jun 25, 2026

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​@​astrojs/​starlight@​0.40.0 ⏵ 0.41.093 -510085 +195100
Updatednpm/​astro@​6.4.7 ⏵ 7.0.2881008898 +1100
Addednpm/​wrangler@​4.104.0991009296100
Addednpm/​astro-mermaid@​2.1.09510010093100

View full report

@socket-security

socket-security Bot commented Jun 25, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm astro is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: website/docs/package-lock.jsonnpm/astro@7.0.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/astro@7.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm js-yaml is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: website/docs/package-lock.jsonnpm/astro@7.0.2npm/@astrojs/starlight@0.41.0npm/js-yaml@4.2.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

sharp is unused directly — no imports; Astro bundles its own copy for
astro:assets image optimization. Docs builds clean without it.

Signed-off-by: Marvin Hansen <marvin.hansen@gmail.com>
@marvin-hansen marvin-hansen merged commit 0733c13 into deepcausality-rs:main Jun 25, 2026
12 of 13 checks passed
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