Skip to content

chore(deps): bump the github-actions group across 1 directory with 6 updates#1625

Merged
julien-deramond merged 2 commits into
mainfrom
dependabot/npm_and_yarn/github-actions-27ce506b2b
May 24, 2026
Merged

chore(deps): bump the github-actions group across 1 directory with 6 updates#1625
julien-deramond merged 2 commits into
mainfrom
dependabot/npm_and_yarn/github-actions-27ce506b2b

Conversation

@dependabot
Copy link
Copy Markdown
Contributor

@dependabot dependabot Bot commented on behalf of github May 15, 2026 •
edited
Loading

Bumps the github-actions group with 6 updates in the / directory:

Package From To
@astrojs/starlight 0.38.5 0.39.2
@astrojs/vercel 10.0.6 10.0.7
astro 6.2.2 6.3.3
tsx 4.21.0 4.22.1
vercel 53.2.0 54.1.0
vitest 4.1.5 4.1.6

Updates @astrojs/starlight from 0.38.5 to 0.39.2

Release notes

Sourced from @​astrojs/starlight's releases.

@​astrojs/starlight@​0.39.2

Patch Changes

@​astrojs/starlight@​0.39.1

Patch Changes

  • #3885 010eed1 Thanks @​ArmandPhilippot! - Fixes the version mentioned in an error message related to autogenerated sidebar groups support.

  • #3887 b3c6990 Thanks @​delucis! - Adds 13 new icons: clock, desktop, mobile-android, window, database, server, code-branch, notes, question, question-circle, analytics, padlock, and solidjs.

@​astrojs/starlight@​0.39.0

Minor Changes

  • #3618 dcf6d09 Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: This release changes how autogenerated links work in Starlight’s sidebar configuration.

    If you have sidebar groups using the autogenerate key, you must now wrap that configuration in an items array:

    {
    label: 'My group',
-   autogenerate: { directory: 'some-dir' },
+   items: [{ autogenerate: { directory: 'some-dir' } }],
}

    This change unlocks the possibility to mix autogenerated links and other links in a single group, for example:

    {
  label: 'Mixed group',
  items: [
    'example-page',
    { autogenerate: { directory: 'examples' } },
    { label: 'More examples', link: 'https://example.com' },
  ],
}

    This release also updates the shape of autogenerated sidebar entries in route data. Autogenerated links and groups in Astro.locals.starlightRoute.sidebar now include an autogenerate object with the configured directory value:

    {
  type: 'link',
  label: 'Example',
  href: '/examples/example/',
  isCurrent: false,
  autogenerate: { directory: 'examples' }
}

... (truncated)

Changelog

Sourced from @​astrojs/starlight's changelog.

0.39.2

Patch Changes

0.39.1

Patch Changes

  • #3885 010eed1 Thanks @​ArmandPhilippot! - Fixes the version mentioned in an error message related to autogenerated sidebar groups support.

  • #3887 b3c6990 Thanks @​delucis! - Adds 13 new icons: clock, desktop, mobile-android, window, database, server, code-branch, notes, question, question-circle, analytics, padlock, and solidjs.

0.39.0

Minor Changes

  • #3618 dcf6d09 Thanks @​HiDeoo! - ⚠️ BREAKING CHANGE: This release changes how autogenerated links work in Starlight’s sidebar configuration.

    If you have sidebar groups using the autogenerate key, you must now wrap that configuration in an items array:

    {
    label: 'My group',
-   autogenerate: { directory: 'some-dir' },
+   items: [{ autogenerate: { directory: 'some-dir' } }],
}

    This change unlocks the possibility to mix autogenerated links and other links in a single group, for example:

    {
  label: 'Mixed group',
  items: [
    'example-page',
    { autogenerate: { directory: 'examples' } },
    { label: 'More examples', link: 'https://example.com' },
  ],
}

    This release also updates the shape of autogenerated sidebar entries in route data. Autogenerated links and groups in Astro.locals.starlightRoute.sidebar now include an autogenerate object with the configured directory value:

    {
  type: 'link',
  label: 'Example',
  href: '/examples/example/',

... (truncated)

Commits

Updates @astrojs/vercel from 10.0.6 to 10.0.7

Release notes

Sourced from @​astrojs/vercel's releases.

@​astrojs/vercel@​10.0.7

Patch Changes

  • Updated dependencies [d365c97]:
    • @​astrojs/internal-helpers@​0.9.1
Changelog

Sourced from @​astrojs/vercel's changelog.

10.0.7

Patch Changes

  • Updated dependencies [d365c97]:
    • @​astrojs/internal-helpers@​0.9.1
Commits

Updates astro from 6.2.2 to 6.3.3

Release notes

Sourced from astro's releases.

astro@6.3.3

Patch Changes

  • #16737 bd84f33 Thanks @​matthewp! - Fixes a reflected XSS vulnerability where slot names on hydrated components were not HTML-escaped in SSR output

astro@6.3.2

Patch Changes

  • #16675 11d4592 Thanks @​ascorbic! - Fixes a regression where Astro.cache was undefined when experimental.cache was not configured.

    The previous documented behavior is for Astro.cache to always be defined as a no-op shim: cache.set() warns once, cache.invalidate() throws and cache.enabled can be used to gate. This allows library and user code can call cache methods without conditional checks. The cache provider registration was being gated at the call site on experimental.cache being configured, which meant the disabled shim branch inside the provider was unreachable and the Astro.cache getter was never attached to the context.

  • #16691 0f0a4ce Thanks @​matthewp! - Fixes HTMLElement is not defined error during HMR when using components with client-side scripts (e.g. Starlight <Tabs>) and the Cloudflare adapter

  • #16562 07529ec Thanks @​matthewp! - Fixes non-prerendered routes failing when a dynamic prerendered route exists in the same project with prerenderEnvironment: 'node'

  • #16638 272185b Thanks @​ematipico! - Fixes a bug where the Astro compiler wasn't freed at the end of the build. After the fix, the memory used by the compiler is now correctly freed at the end of the build.

  • #16544 d365c97 Thanks @​matthewp! - Tightens isRemotePath() to reject control characters after a leading slash and fixes the dev image endpoint origin check

  • #16685 889e748 Thanks @​farrosfr! - Improve validation messages for security.csp.directives when script-src or style-src are incorrectly placed in the directives array.

  • #16605 772f13a Thanks @​rururux! - Fixes assetsPrefix not being available on build from astro:config/server.

  • #16556 f38dec7 Thanks @​matthewp! - Rejects double-encoded URL paths with a 400 response instead of silently falling back to partial decoding

  • #16659 38bcb25 Thanks @​jsparkdev! - Fixes & characters appearing as raw entity strings (e.g. &[#38](https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/38);) in <meta> tags when viewed in link previews or raw HTML.

  • Updated dependencies [d365c97, 9256345]:

    • @​astrojs/internal-helpers@​0.9.1
    • @​astrojs/markdown-remark@​7.1.2

astro@6.3.1

Patch Changes

  • #16646 15fbc41 Thanks @​matthewp! - Fixes local images returning 404 on non-prerendered pages when using the generic image endpoint

astro@6.3.0

Minor Changes

  • #16366 d69f858 Thanks @​matthewp! - Adds a new experimental.advancedRouting option that lets you take full control of Astro's request handling pipeline by creating a src/app.ts file in your project.

    Today, Astro handles every incoming request through a fixed internal pipeline: trailing slash normalization, redirects, actions, middleware, page rendering, i18n, and so on. That pipeline works great for most sites, but as projects grow you often want to run your own logic between those steps — an auth check before rendering, a rate limiter before actions, custom logging around the whole stack. Advanced routing gives you that control.

    When enabled, Astro looks for a src/app.ts file in your project. If it finds one, that file becomes the entrypoint for all server-rendered requests. You compose the pipeline yourself using the handlers Astro provides, and you can slot your own logic anywhere in the chain.

    Enabling advanced routing

    // astro.config.mjs

... (truncated)

Changelog

Sourced from astro's changelog.

6.3.3

Patch Changes

  • #16737 bd84f33 Thanks @​matthewp! - Fixes a reflected XSS vulnerability where slot names on hydrated components were not HTML-escaped in SSR output

6.3.2

Patch Changes

  • #16675 11d4592 Thanks @​ascorbic! - Fixes a regression where Astro.cache was undefined when experimental.cache was not configured.

    The previous documented behavior is for Astro.cache to always be defined as a no-op shim: cache.set() warns once, cache.invalidate() throws and cache.enabled can be used to gate. This allows library and user code can call cache methods without conditional checks. The cache provider registration was being gated at the call site on experimental.cache being configured, which meant the disabled shim branch inside the provider was unreachable and the Astro.cache getter was never attached to the context.

  • #16691 0f0a4ce Thanks @​matthewp! - Fixes HTMLElement is not defined error during HMR when using components with client-side scripts (e.g. Starlight <Tabs>) and the Cloudflare adapter

  • #16562 07529ec Thanks @​matthewp! - Fixes non-prerendered routes failing when a dynamic prerendered route exists in the same project with prerenderEnvironment: 'node'

  • #16638 272185b Thanks @​ematipico! - Fixes a bug where the Astro compiler wasn't freed at the end of the build. After the fix, the memory used by the compiler is now correctly freed at the end of the build.

  • #16544 d365c97 Thanks @​matthewp! - Tightens isRemotePath() to reject control characters after a leading slash and fixes the dev image endpoint origin check

  • #16685 889e748 Thanks @​farrosfr! - Improve validation messages for security.csp.directives when script-src or style-src are incorrectly placed in the directives array.

  • #16605 772f13a Thanks @​rururux! - Fixes assetsPrefix not being available on build from astro:config/server.

  • #16556 f38dec7 Thanks @​matthewp! - Rejects double-encoded URL paths with a 400 response instead of silently falling back to partial decoding

  • #16659 38bcb25 Thanks @​jsparkdev! - Fixes & characters appearing as raw entity strings (e.g. &[#38](https://github.com/withastro/astro/tree/HEAD/packages/astro/issues/38);) in <meta> tags when viewed in link previews or raw HTML.

  • Updated dependencies [d365c97, 9256345]:

    • @​astrojs/internal-helpers@​0.9.1
    • @​astrojs/markdown-remark@​7.1.2

6.3.1

Patch Changes

  • #16646 15fbc41 Thanks @​matthewp! - Fixes local images returning 404 on non-prerendered pages when using the generic image endpoint

6.3.0

Minor Changes

  • #16366 d69f858 Thanks @​matthewp! - Adds a new experimental.advancedRouting option that lets you take full control of Astro's request handling pipeline by creating a src/app.ts file in your project.

    Today, Astro handles every incoming request through a fixed internal pipeline: trailing slash normalization, redirects, actions, middleware, page rendering, i18n, and so on. That pipeline works great for most sites, but as projects grow you often want to run your own logic between those steps — an auth check before rendering, a rate limiter before actions, custom logging around the whole stack. Advanced routing gives you that control.

    When enabled, Astro looks for a src/app.ts file in your project. If it finds one, that file becomes the entrypoint for all server-rendered requests. You compose the pipeline yourself using the handlers Astro provides, and you can slot your own logic anywhere in the chain.

... (truncated)

Commits

Updates tsx from 4.21.0 to 4.22.1

Release notes

Sourced from tsx's releases.

v4.22.1

4.22.1 (2026-05-17)

Bug Fixes

  • resolve tsconfig path aliases containing a colon (#780) (6979f28)

This release is also available on:

v4.22.0

4.22.0 (2026-05-14)

Features

This release is also available on:

v4.21.1

4.21.1 (2026-05-14)

Bug Fixes

  • support Node 20.11/21.2 import.meta paths (acf3d8f)
  • support Node.js 24.15.0 (c1d2d45)
  • support Node.js 26.1.0 and 25.9.0 (1d7e528)

This release is also available on:

Commits
  • 6979f28 fix: resolve tsconfig path aliases containing a colon (#780)
  • b29f6ee feat: upgrade esbuild to 0.28 (#789)
  • 0dd17e9 test: cover registerHooks loader composition
  • acf3d8f fix: support Node 20.11/21.2 import.meta paths
  • 4bbef80 test: cover configDir paths without baseUrl
  • dddc5ce test: cover sync-hook watch reruns and cleanup retries
  • 09e8f8c test: assert CLI runs without warnings
  • 1d7e528 fix: support Node.js 26.1.0 and 25.9.0
  • c1d2d45 fix: support Node.js 24.15.0
  • d04672d test: update node version feature gates
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for tsx since your current version.


Updates vercel from 53.2.0 to 54.1.0

Release notes

Sourced from vercel's releases.

vercel@54.1.0

Minor Changes

  • 9aead7a: Add vercel connect detach to detach a Vercel project from a connector via DELETE /v1/connect/connectors/:id/projects/:projectId. Mirrors vercel connect attach and matches the project-scope "Disconnect" button in the dashboard.

    Add --triggers, --trigger-branch, and --trigger-path flags to vercel connect attach. When --triggers is set, the project is also registered as a trigger destination on the connector via PATCH /v1/connect/connectors/:id/trigger-destinations so verified webhooks get forwarded to it. Requires the connector to support triggers; warns if the connector was created without triggers.enabled.

    Both features gated behind the existing FF_CONNEX_ENABLED flag.

  • b1db109: Enable vercel connect by default and mark it as beta in --help. The command was previously gated behind the internal FF_CONNEX_ENABLED env var; it is now available out of the box and surfaces in vercel --help as connect [cmd] Manage connectors [beta]. The subcommand description also reads Manage connectors (Beta).

    Fix vercel connect open to link to the renamed /~/connect/ dashboard route directly instead of relying on the legacy /~/connex/ → /~/connect/ 308 redirect.

  • e8deaa1: Rename vercel connex command to vercel connect. The command remains gated behind the existing FF_CONNEX_ENABLED flag.

  • cc30efd: Refresh the vc setup-and-link flow and post-deploy output for clarity and visual consistency.

    Prompt copy

    • Want to modify these settings? → Customize settings?.
    • Which scope should contain your project? → Which team?. Matches dashboard + docs vocabulary.
    • What's your project's name? → Name?. The directory-derived default still renders inline via the inquirer default.
    • Loading scopes… spinner → Loading teams….

    Flow changes

    • Removed the Set up and deploy "/path"? confirmation prompt. Intent is implied by running vc; the path is surfaced as a status line ( Set up "/path") and Ctrl-C remains the escape hatch.
    • The In which directory is your code located? prompt now fires when (a) the current directory is a workspace (monorepo with multiple packages), (b) the user explicitly chose "Choose a different root directory" via the inferred-services picker, or (c) framework detection at the root finds nothing — covers nested-monolith layouts like repo/app/package.json where the app lives in a subdir. Single-app projects with a framework detected at the root still default the root to . and skip the prompt.

    Output format

    • Auto-detected Project Settings for X line replaced with a single bold Detected X (Build Command: …, Output Directory: …) line. Title Case labels match the checkbox panel below. Only Detected is bold; framework name and parens render plain/dim.
    • Introduced a new aligned-label format for status output via the printAlignedLabel helper (12-char bold label column, value column at terminal column 14). Applied to Linked / Inspect / Production / Preview / Aliased / Added rows.
    • vc redeploy output now uses the same aligned-label format as vc deploy — Inspect / Production / Preview / Aliased rows are consistent across both commands. No more emoji-prefix / aligned-label mixing in the same session.
    • vc link --repo info messages (No Projects are linked…, Found N Project(s) linked…, Detected N new Project(s)…, Created new Project: …) dropped the gray > prefix and now use the 2-space indent that matches the rest of the link/setup flow.
    • Path-in-prompt for vc link --repo confirm message uses chalk.dim instead of chalk.cyan — paths are not URLs, so dim is the correct treatment per the color rules (cyan reserved for URLs).
    • Introduced a "gutter" semantic system: column 0 is reserved for semantic glyphs. ▲ marks Production deploys (▲ Production URL) and breaks out of the indent — bookending the session with the ▲ brand mark at the top. Preview deploys stay in-column without the triangle.
    • Added a terminal ✓ Ready in Xs line at deploy completion (green ✓ at column 0, bold Ready, dim duration). Skipped when --no-wait is set and the deployment hasn't reached READY yet.
    • Dropped the emoji prefixes (🔗, 🔍, ⏳) on Linked / Inspect / Production rows (across both vc deploy and vc redeploy).
    • Dropped the Building: prefix from the build-logs spinner. Each streamed log line is shown verbatim instead of Building: <line>.
    • Dropped the (created .vercel and added it to .gitignore) parenthetical from Linked — git status surfaces it on demand.
    • Dropped the [Xs] timing suffix from URL lines. URLs are results, not operations — timing belongs on the build / ready signal.

    Defensive fix

    • services-setup.ts now uses an optional chain on detectServicesResult.resolved?.source. This was crashing the setup flow before any prompts could fire when no services were detected (common for empty or simple fixtures).

    New helper

    • packages/cli/src/util/output/print-aligned-label.ts exports printAlignedLabel(label, value, options?: { gutter?: string }) and the ALIGNED_LABEL_WIDTH constant (12). Used by every aligned-row print site.

... (truncated)

Changelog

Sourced from vercel's changelog.

54.1.0

Minor Changes

  • 9aead7a: Add vercel connect detach to detach a Vercel project from a connector via DELETE /v1/connect/connectors/:id/projects/:projectId. Mirrors vercel connect attach and matches the project-scope "Disconnect" button in the dashboard.

    Add --triggers, --trigger-branch, and --trigger-path flags to vercel connect attach. When --triggers is set, the project is also registered as a trigger destination on the connector via PATCH /v1/connect/connectors/:id/trigger-destinations so verified webhooks get forwarded to it. Requires the connector to support triggers; warns if the connector was created without triggers.enabled.

    Both features gated behind the existing FF_CONNEX_ENABLED flag.

  • b1db109: Enable vercel connect by default and mark it as beta in --help. The command was previously gated behind the internal FF_CONNEX_ENABLED env var; it is now available out of the box and surfaces in vercel --help as connect [cmd] Manage connectors [beta]. The subcommand description also reads Manage connectors (Beta).

    Fix vercel connect open to link to the renamed /~/connect/ dashboard route directly instead of relying on the legacy /~/connex/ → /~/connect/ 308 redirect.

  • e8deaa1: Rename vercel connex command to vercel connect. The command remains gated behind the existing FF_CONNEX_ENABLED flag.

  • cc30efd: Refresh the vc setup-and-link flow and post-deploy output for clarity and visual consistency.

    Prompt copy

    • Want to modify these settings? → Customize settings?.
    • Which scope should contain your project? → Which team?. Matches dashboard + docs vocabulary.
    • What's your project's name? → Name?. The directory-derived default still renders inline via the inquirer default.
    • Loading scopes… spinner → Loading teams….

    Flow changes

    • Removed the Set up and deploy "/path"? confirmation prompt. Intent is implied by running vc; the path is surfaced as a status line ( Set up "/path") and Ctrl-C remains the escape hatch.
    • The In which directory is your code located? prompt now fires when (a) the current directory is a workspace (monorepo with multiple packages), (b) the user explicitly chose "Choose a different root directory" via the inferred-services picker, or (c) framework detection at the root finds nothing — covers nested-monolith layouts like repo/app/package.json where the app lives in a subdir. Single-app projects with a framework detected at the root still default the root to . and skip the prompt.

    Output format

    • Auto-detected Project Settings for X line replaced with a single bold Detected X (Build Command: …, Output Directory: …) line. Title Case labels match the checkbox panel below. Only Detected is bold; framework name and parens render plain/dim.
    • Introduced a new aligned-label format for status output via the printAlignedLabel helper (12-char bold label column, value column at terminal column 14). Applied to Linked / Inspect / Production / Preview / Aliased / Added rows.
    • vc redeploy output now uses the same aligned-label format as vc deploy — Inspect / Production / Preview / Aliased rows are consistent across both commands. No more emoji-prefix / aligned-label mixing in the same session.
    • vc link --repo info messages (No Projects are linked…, Found N Project(s) linked…, Detected N new Project(s)…, Created new Project: …) dropped the gray > prefix and now use the 2-space indent that matches the rest of the link/setup flow.
    • Path-in-prompt for vc link --repo confirm message uses chalk.dim instead of chalk.cyan — paths are not URLs, so dim is the correct treatment per the color rules (cyan reserved for URLs).
    • Introduced a "gutter" semantic system: column 0 is reserved for semantic glyphs. ▲ marks Production deploys (▲ Production URL) and breaks out of the indent — bookending the session with the ▲ brand mark at the top. Preview deploys stay in-column without the triangle.
    • Added a terminal ✓ Ready in Xs line at deploy completion (green ✓ at column 0, bold Ready, dim duration). Skipped when --no-wait is set and the deployment hasn't reached READY yet.
    • Dropped the emoji prefixes (🔗, 🔍, ⏳) on Linked / Inspect / Production rows (across both vc deploy and vc redeploy).
    • Dropped the Building: prefix from the build-logs spinner. Each streamed log line is shown verbatim instead of Building: <line>.
    • Dropped the (created .vercel and added it to .gitignore) parenthetical from Linked — git status surfaces it on demand.
    • Dropped the [Xs] timing suffix from URL lines. URLs are results, not operations — timing belongs on the build / ready signal.

    Defensive fix

    • services-setup.ts now uses an optional chain on detectServicesResult.resolved?.source. This was crashing the setup flow before any prompts could fire when no services were detected (common for empty or simple fixtures).

    New helper

    • packages/cli/src/util/output/print-aligned-label.ts exports printAlignedLabel(label, value, options?: { gutter?: string }) and the ALIGNED_LABEL_WIDTH constant (12). Used by every aligned-row print site.

... (truncated)

Commits

Updates vitest from 4.1.5 to 4.1.6

Release notes

Sourced from vitest's releases.

v4.1.6

   🐞 Bug Fixes

   🏎 Performance

    View changes on GitHub
Commits
  • a8fd24c chore: release v4.1.6
  • 18af98c fix(browser): simplify orchestrator otel carrier (#10285)
  • 3188260 feat(browser): provide project reference in ToMatchScreenshotResolvePath (#...
  • See full diff in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels May 15, 2026
@vercel
Copy link
Copy Markdown

vercel Bot commented May 15, 2026 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
openresource-dev Ready Ready Preview, Comment May 24, 2026 9:19am

@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/github-actions-27ce506b2b branch from 088cffa to b0b6d4d Compare May 21, 2026 20:20
@julien-deramond
Copy link
Copy Markdown
Member

julien-deramond commented May 24, 2026

@dependabot rebase

@dependabot
chore(deps): bump the github-actions group across 1 directory with 6 …
8228771 
…updates

Bumps the github-actions group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [@astrojs/starlight](https://github.com/withastro/starlight/tree/HEAD/packages/starlight) | `0.38.5` | `0.39.2` |
| [@astrojs/vercel](https://github.com/withastro/astro/tree/HEAD/packages/integrations/vercel) | `10.0.6` | `10.0.7` |
| [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro) | `6.2.2` | `6.3.3` |
| [tsx](https://github.com/privatenumber/tsx) | `4.21.0` | `4.22.1` |
| [vercel](https://github.com/vercel/vercel/tree/HEAD/packages/cli) | `53.2.0` | `54.1.0` |
| [vitest](https://github.com/vitest-dev/vitest/tree/HEAD/packages/vitest) | `4.1.5` | `4.1.6` |



Updates `@astrojs/starlight` from 0.38.5 to 0.39.2
- [Release notes](https://github.com/withastro/starlight/releases)
- [Changelog](https://github.com/withastro/starlight/blob/main/packages/starlight/CHANGELOG.md)
- [Commits](https://github.com/withastro/starlight/commits/@astrojs/starlight@0.39.2/packages/starlight)

Updates `@astrojs/vercel` from 10.0.6 to 10.0.7
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/vercel/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/vercel@10.0.7/packages/integrations/vercel)

Updates `astro` from 6.2.2 to 6.3.3
- [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.3.3/packages/astro)

Updates `tsx` from 4.21.0 to 4.22.1
- [Release notes](https://github.com/privatenumber/tsx/releases)
- [Changelog](https://github.com/privatenumber/tsx/blob/master/release.config.cjs)
- [Commits](privatenumber/tsx@v4.21.0...v4.22.1)

Updates `vercel` from 53.2.0 to 54.1.0
- [Release notes](https://github.com/vercel/vercel/releases)
- [Changelog](https://github.com/vercel/vercel/blob/main/packages/cli/CHANGELOG.md)
- [Commits](https://github.com/vercel/vercel/commits/vercel@54.1.0/packages/cli)

Updates `vitest` from 4.1.5 to 4.1.6
- [Release notes](https://github.com/vitest-dev/vitest/releases)
- [Changelog](https://github.com/vitest-dev/vitest/blob/main/docs/releases.md)
- [Commits](https://github.com/vitest-dev/vitest/commits/v4.1.6/packages/vitest)

---
updated-dependencies:
- dependency-name: "@astrojs/starlight"
  dependency-version: 0.39.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: "@astrojs/vercel"
  dependency-version: 10.0.7
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
- dependency-name: astro
  dependency-version: 6.3.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: tsx
  dependency-version: 4.22.0
  dependency-type: direct:development
  update-type: version-update:semver-minor
  dependency-group: github-actions
- dependency-name: vercel
  dependency-version: 54.0.0
  dependency-type: direct:development
  update-type: version-update:semver-major
  dependency-group: github-actions
- dependency-name: vitest
  dependency-version: 4.1.6
  dependency-type: direct:development
  update-type: version-update:semver-patch
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot force-pushed the dependabot/npm_and_yarn/github-actions-27ce506b2b branch from b0b6d4d to 8228771 Compare May 24, 2026 09:17
@julien-deramond julien-deramond merged commit e9ef164 into main May 24, 2026
4 checks passed
@julien-deramond julien-deramond deleted the dependabot/npm_and_yarn/github-actions-27ce506b2b branch May 24, 2026 09:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@julien-deramond julien-deramond julien-deramond approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@julien-deramond