chore(deps): bump the npm_and_yarn group across 2 directories with 2 updates#972
chore(deps): bump the npm_and_yarn group across 2 directories with 2 updates#972dependabot[bot] wants to merge 1 commit into
Conversation
…updates Bumps the npm_and_yarn group with 1 update in the /apps/site directory: [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro). Bumps the npm_and_yarn group with 1 update in the /examples/basic directory: [vite](https://github.com/vitejs/vite/tree/HEAD/packages/vite). Updates `astro` from 5.16.13 to 6.1.6 - [Release notes](https://github.com/withastro/astro/releases) - [Changelog](https://github.com/withastro/astro/blob/main/packages/astro/CHANGELOG.md) - [Commits](https://github.com/withastro/astro/commits/astro@6.1.6/packages/astro) Updates `vite` from 7.2.4 to 7.3.2 - [Release notes](https://github.com/vitejs/vite/releases) - [Changelog](https://github.com/vitejs/vite/blob/v7.3.2/packages/vite/CHANGELOG.md) - [Commits](https://github.com/vitejs/vite/commits/v7.3.2/packages/vite) --- updated-dependencies: - dependency-name: astro dependency-version: 6.1.6 dependency-type: direct:production dependency-group: npm_and_yarn - dependency-name: vite dependency-version: 7.3.2 dependency-type: direct:development dependency-group: npm_and_yarn ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
samui-wallet-web | 8fcfbb4 | Commit Preview URL Branch Preview URL |
Apr 21 2026, 10:26 PM |
📝 WalkthroughWalkthroughTwo package.json dependency versions were updated: Astro from 5.16.13 to 6.1.6 in Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@apps/site/package.json`:
- Line 6: Update the Starlight dependency in apps/site package.json to a version
compatible with Astro 6 (bump `@astrojs/starlight` to 0.38.0 or later) so it
matches the existing "astro": "6.1.6" entry; after bumping `@astrojs/starlight`,
run dependency install and validate the site build, then review content loader
usage (e.g., docsLoader in src/content.config.ts) and any schema/zod usages to
ensure compatibility with Starlight 0.38.0 and Astro 6 before merging.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 8a8e0fa6-aa22-4ccb-b59d-bd90b5a64c92
📒 Files selected for processing (2)
apps/site/package.jsonexamples/basic/package.json
| "@astrojs/starlight-tailwind": "4.0.2", | ||
| "@tailwindcss/vite": "catalog:", | ||
| "astro": "5.16.13", | ||
| "astro": "6.1.6", |
There was a problem hiding this comment.
🧩 Analysis chain
🌐 Web query:
What are the breaking changes in Astro 6 compared to Astro 5 and what migration steps are required?
💡 Result:
Astro 6 introduces several breaking changes compared to Astro 5, primarily documented in the official upgrade guide. Key changes include dependency upgrades, removal of legacy features, changed defaults, and specific API modifications. Migration involves updating Node.js, dependencies, config flags, and code patterns. ## Dependency Upgrades (high impact) - Node.js: Drops support for Node 18 (EOL March 2025) and Node 20 (EOL April 2026). Requires Node 22.12.0+. Update your .nvmrc or deployment env: 22.12.0 - Vite 7.0: As dev server and bundler. Check Vite migration guide if using custom Vite plugins/config. - Zod 4: For content schema validation. Import Zod from astro/zod. Update schemas for Zod 4 breaking changes (e.g., deprecated async schema functions; use static schema property). - Shiki v4: For syntax highlighting. Update integrations like @astrojs adapters (Cloudflare, Netlify, etc.) for compatibility. ## Legacy Features Removed/Deprecated - Legacy Content Collections: Automatic backwards compatibility and legacy.collections flag removed. Migrate all to Content Layer API (src/content.config.ts). Use loaders like glob for filesystem content. - Astro object in getStaticPaths: Deprecated; use astro:config virtual module instead. - ViewTransitions: → ; removed deprecated exports from astro:transitions. - CommonJS config files: ESM-only now. - Removed experimental flags now stable: csp, liveCollections, preserveScriptOrder, headingIdCompat, etc. Remove from astro.config.mjs. ## Changed Defaults - i18n.routing.redirectToDefaultLocale: Now false (was true). - Image service: Cropping always enabled (no fit required); generates styles at build-time (data-astro-fit/pos attributes). - <script> and <style> tags: Render in declaration order (hoisted before). ## Breaking Changes - Endpoints with file extensions (e.g., api/user.json): No trailing slash access (e.g., /api/user.json/ → 404). - import.meta.env: Always inlined strings (no type coercion like "true"→boolean). - Assets: Always crop, never upscale. Remove fit: 'contain' if used for cropping. - Markdown: Heading IDs no longer strip trailing hyphens (e.g., ## Heading-- → heading--). - SSRManifest: Path properties changed. - Adapter/Integration API: Removed hooks like entryPoints/routes; new Adapter API with setAdapter({entryType: 'self'}); deprecated createExports/start. - Removed: emitESMImage, session test driver, prefetch 'with' option. ## Migration Steps 1. Run npx @astrojs/upgrade (automated tool) or npm install astro@latest. 2. Update Node to 22.12.0+ locally and in deployment. 3. Remove legacy/experimental flags from astro.config.mjs. 4. Migrate content collections to Content Layer API if using legacy src/content/. 5. Update Zod schemas: Import from astro/zod; fix async schemas. 6. Check images: Remove unnecessary fit: 'contain'. 7. Update ViewTransitions to ClientRouter. 8. Test i18n routing defaults. 9. Review adapters/integrations changelogs. 10. Run astro check, astro build, astro preview; fix errors. Full details: Official upgrade guide and changelog. Most projects migrate smoothly; content-heavy sites need Content Layer updates. Zod 4 may break third-party loaders.
Citations:
- 1: https://docs.astro.build/en/guides/upgrade-to/v6/
- 2: https://astro.build/blog/astro-6/
- 3: https://github.com/withastro/astro/releases/tag/astro%406.0.0
- 4: https://www.astrov.icu
- 5: https://github.com/withastro/astro/releases/tag/astro%406.0.6
- 6: https://github.com/withastro/astro/releases/tag/astro%406.1.0
- 7: https://github.com/withastro/astro/blob/refs/heads/next/packages/astro/CHANGELOG.md
🌐 Web query:
Is @astrojs/starlight version 0.37.4 compatible with Astro 6.1.6?
💡 Result:
No, @astrojs/starlight version 0.37.4 is not compatible with Astro 6.1.6. Starlight 0.37.x requires Astro 5.x, as indicated by its dev dependencies on astro ^5.x and the absence of Astro 6 support announcements in its release notes. Astro 6 support was added in Starlight 0.38.0, which explicitly drops Astro 5 support and requires Astro ^6.0.0. Using Starlight 0.37.4 with Astro 6 may result in compatibility issues due to breaking changes in Astro 6.
Citations:
- 1: Astro 6 support withastro/starlight#3644
- 2: https://github.com/withastro/starlight/releases
- 3: https://www.npmjs.com/package/@astrojs/starlight?activeTab=code
- 4: https://starlight-changelog.netlify.app/
- 5: https://registry.npmjs.org/%40astrojs%2Fstarlight
- 6: https://github.com/withastro/starlight/blob/5387d33b/packages/starlight/CHANGELOG.md
- 7: https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md
- 8: https://github.com/withastro/starlight/releases/tag/%40astrojs%2Fstarlight%400.38.0
🏁 Script executed:
#!/bin/bash
# Description: Check for Astro API usage patterns that might be affected by v6 upgrade
echo "=== Checking Content Collections API usage ==="
rg -n --type=ts --type=js "defineCollection|docsLoader|getCollection" apps/site/
echo -e "\n=== Checking Astro config patterns ==="
rg -n --type=js --type=mjs "defineConfig|redirects" apps/site/
echo -e "\n=== Checking Astro runtime API usage ==="
rg -n "Astro\.(locals|props|request|response|cookies)" apps/site/Repository: samui-build/samui-wallet
Length of output: 623
🏁 Script executed:
#!/bin/bash
# Read astro.config.mjs to check for defineConfig and redirects
echo "=== Checking astro.config.mjs content ==="
if [ -f "apps/site/astro.config.mjs" ]; then
cat -n "apps/site/astro.config.mjs"
else
echo "File not found"
find apps/site -name "astro.config.*" -type f
fiRepository: samui-build/samui-wallet
Length of output: 2170
🌐 Web query:
Is Astro.locals API still available and compatible in Astro 6?
💡 Result:
Yes, the Astro.locals API is still available and fully compatible in Astro 6.
Citations:
- 1: https://docs.astro.build/en/reference/api-reference/
- 2: https://docs.astro.build/hi/guides/middleware
- 3: https://v4.docs.astro.build/en/reference/api-reference/
- 4: https://v6.docs.astro.build/hi/guides/middleware/
- 5: https://v6.docs.astro.build/en/guides/middleware/
- 6: https://docs.astro.build/en/reference/modules/astro-middleware
- 7: https://docs.astro.build/en/guides/middleware/
🌐 Web query:
Does Astro 6 with Vite 7 resolve the Vite 6 incompatibility issues?
💡 Result:
Yes, Astro 6 with Vite 7 resolves the Vite 6 incompatibility issues.
Citations:
- 1: Upgrade to Astro 6 + Vite 7 + Tailwind 4.2 llbbl/semantic-docs#33
- 2: https://v6.docs.astro.build/fr/guides/upgrade-to/v6/
- 3: https://astro.build/blog/astro-6/
- 4: https://github.com/withastro/astro/releases/tag/%40astrojs/vue%406.0.0
- 5: Update Vite peer dependency to v7 withastro/astro#14362
- 6: https://docs.astro.build/en/guides/upgrade-to/v6/
Starlight 0.37.4 is incompatible with Astro 6.1.6—upgrade to Starlight 0.38.0+ is required.
The codebase cannot upgrade to Astro 6.1.6 while using @astrojs/starlight 0.37.4. Starlight 0.37.x requires Astro 5.x; Astro 6 support was added in Starlight 0.38.0, which drops Astro 5 support and requires astro ^6.0.0. Both dependencies must be updated together.
Beyond the Starlight blocker, Astro 6 introduces extensive breaking changes that require migration:
- Node.js: Drops support for Node 18 and 20; requires Node 22.12.0+
- Content Collections: The
docsLoader()pattern insrc/content.config.tsrequires verification against Starlight 0.38.0's loader API - Vite upgrade: Astro 6 bundles Vite 7, which resolves the current Vite 6 vs 7 incompatibility flagged in
astro.config.mjsline 61 (the@ts-expect-errorcomment becomes unnecessary) - Zod 4: Required for schema validation; may break custom loaders
- Config defaults:
i18n.routing.redirectToDefaultLocalenow defaults tofalse; image cropping behavior changed
Verify that Starlight 0.38.0's loader implementation is compatible with your current content structure before proceeding.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@apps/site/package.json` at line 6, Update the Starlight dependency in
apps/site package.json to a version compatible with Astro 6 (bump
`@astrojs/starlight` to 0.38.0 or later) so it matches the existing "astro":
"6.1.6" entry; after bumping `@astrojs/starlight`, run dependency install and
validate the site build, then review content loader usage (e.g., docsLoader in
src/content.config.ts) and any schema/zod usages to ensure compatibility with
Starlight 0.38.0 and Astro 6 before merging.
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/npm_and_yarn/apps/site/npm_and_yarn-d08254cda0
branch
Bumps the npm_and_yarn group with 1 update in the /apps/site directory: astro.
Bumps the npm_and_yarn group with 1 update in the /examples/basic directory: vite.
Updates
astrofrom 5.16.13 to 6.1.6Release notes
Sourced from astro's releases.
... (truncated)
Changelog
Sourced from astro's changelog.
... (truncated)
Commits
1945a93[ci] release (#16281)bb4586afix: avoid full-reload in scss modules (#14924)5f3085b[ci] formatb5c2fbaSkip actions server-output validation when an adapter is configured (#16202)b06eabfConsolidate inline script escaping into shared utility (#16303)92fc030refactor(core): rename logger internal types (#16271)ba18015[ci] formatd198e82test: port 16 routing unit tests to TypeScript (#16266)673a871[ci] release (#16244)fab9c00chore: upgrade biome (#16246)Updates
vitefrom 7.2.4 to 7.3.2Release notes
Sourced from vite's releases.
Changelog
Sourced from vite's changelog.
Commits
cc383e0release: v7.3.209d8c90fix: avoid path traversal with optimize deps sourcemap handler (#22161)f8103ccfix: checkserver.fsafter stripping query as well (#22160)19db0f2fix: backport #22159, apply server.fs check to env transport (#22162)95e8923release: v7.3.19d39d37feat: addignoreOutdatedRequestsoption tooptimizeDeps(#21364)acf7e05release: v7.3.0cff26ecfeat(deps): update esbuild from ^0.25.0 to ^0.27.0 (#21183)317b3b2release: v7.2.7721f163fix: plugin shortcut support (#21211)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditionsYou can disable automated security fix PRs for this repo from the Security Alerts page.
Summary by CodeRabbit