Skip to content

Bump js-yaml, @astrojs/svelte, @astrojs/vercel, @astrolib/analytics, @astrolib/seo, astro, @astrojs/mdx and @astrojs/tailwind #171

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Bump js-yaml, @astrojs/svelte, @astrojs/vercel, @astrolib/analytics, @astrolib/seo, astro, @astrojs/mdx and @astrojs/tailwind #171

wants to merge 1 commit into from

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Nov 14, 2025

Bumps js-yaml, @astrojs/svelte, @astrojs/vercel, @astrolib/analytics, @astrolib/seo, astro, @astrojs/mdx and @astrojs/tailwind. These dependencies needed to be updated together.
Updates js-yaml from 4.1.0 to 4.1.1

Changelog

Sourced from js-yaml's changelog.

[4.1.1] - 2025-11-12

Security

  • Fix prototype pollution issue in yaml merge (<<) operator.
Commits

Updates @astrojs/svelte from 5.3.0 to 7.2.2

Release notes

Sourced from @​astrojs/svelte's releases.

@​astrojs/svelte@​7.2.2

Patch Changes

  • #14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

@​astrojs/svelte@​7.2.1

Patch Changes

@​astrojs/svelte@​7.2.0

Minor Changes

  • #14430 78011ba Thanks @​ascorbic! - Adds support for async server rendering

    Svelte 5.36 added experimental support for async rendering. This allows you to use await in your components in several new places. This worked out of the box with client-rendered components, but server-rendered components needed some extra help. This update adds support for async server rendering in Svelte components used in Astro.

    To use async rendering, you must enable it in your Svelte config:

    // svelte.config.js
export default {
  compilerOptions: {
    experimental: {
      async: true,
    },
  },
};

    Then you can use await in your components:

    <script>
  let data = await fetch('/api/data').then(res => res.json());
</script>
<h1>{data.title}</h1>

    See the Svelte docs for more information on using await in Svelte components, including inside $derived blocks and directly in markup.

Patch Changes

  • #14433 9cc8f21 Thanks @​ascorbic! - Fixes a bug that prevented Svelte 5.39.1+ components rendering when multiple frameworks were present

@​astrojs/svelte@​7.1.1

... (truncated)

Changelog

Sourced from @​astrojs/svelte's changelog.

7.2.2

Patch Changes

  • #14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

7.2.1

Patch Changes

7.2.0

Minor Changes

  • #14430 78011ba Thanks @​ascorbic! - Adds support for async server rendering

    Svelte 5.36 added experimental support for async rendering. This allows you to use await in your components in several new places. This worked out of the box with client-rendered components, but server-rendered components needed some extra help. This update adds support for async server rendering in Svelte components used in Astro.

    To use async rendering, you must enable it in your Svelte config:

    // svelte.config.js
export default {
  compilerOptions: {
    experimental: {
      async: true,
    },
  },
};

    Then you can use await in your components:

    <script>
  let data = await fetch('/api/data').then(res => res.json());
</script>
<h1>{data.title}</h1>

    See the Svelte docs for more information on using await in Svelte components, including inside $derived blocks and directly in markup.

Patch Changes

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​astrojs/svelte since your current version.


Updates @astrojs/vercel from 7.5.2 to 9.0.0

Release notes

Sourced from @​astrojs/vercel's releases.

@​astrojs/vercel@​8.2.11

Patch Changes

  • #14570 c96711d Thanks @​matthewp! - Fix regression in 8.2.7: validate densities-based srcset widths against configured sizes

    When using densities with the Vercel image adapter, calculated widths were not being validated against Vercel's configured sizes list. This caused images to fail when using densities, as Vercel would reject the invalid widths.

    This fix ensures densities-calculated widths are mapped to valid configured sizes, matching the behavior already implemented for the widths prop.

@​astrojs/vercel@​8.2.10

Patch Changes

@​astrojs/vercel@​8.2.9

Patch Changes

@​astrojs/vercel@​8.2.8

Patch Changes

  • Updated dependencies [1e2499e]:
    • @​astrojs/internal-helpers@​0.7.3

@​astrojs/vercel@​8.2.7

Patch Changes

  • #14039 da4182d Thanks @​ematipico! - Fixes a bug where experimentalStaticHeaders did not work as expected.

  • #14289 ed493a6 Thanks @​ascorbic! - Fixes a bug that caused invalid image sizes to be generated when the requested widths were larger than the source image

@​astrojs/vercel@​8.2.6

Patch Changes

  • Updated dependencies [4d16de7]:
    • @​astrojs/internal-helpers@​0.7.2
Changelog

Sourced from @​astrojs/vercel's changelog.

9.0.0

Major Changes

Minor Changes

  • #14543 9b3241d Thanks @​matthewp! - Enables skew protection for Astro sites deployed on Vercel. Skew protection ensures that your site's client and server versions stay synchronized during deployments, preventing issues where users might load assets from a newer deployment while the server is still running the older version.

    Skew protection is automatically enabled on Vercel deployments when the VERCEL_SKEW_PROTECTION_ENABLED environment variable is set to 1. The deployment ID is automatically included in both asset requests and API calls, allowing Vercel to serve the correct version to every user.

8.2.11

Patch Changes

  • #14570 c96711d Thanks @​matthewp! - Fix regression in 8.2.7: validate densities-based srcset widths against configured sizes

    When using densities with the Vercel image adapter, calculated widths were not being validated against Vercel's configured sizes list. This caused images to fail when using densities, as Vercel would reject the invalid widths.

    This fix ensures densities-calculated widths are mapped to valid configured sizes, matching the behavior already implemented for the widths prop.

8.2.10

Patch Changes

8.2.9

Patch Changes

8.2.8

Patch Changes

  • Updated dependencies [1e2499e]:
    • @​astrojs/internal-helpers@​0.7.3

8.2.7

Patch Changes

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​astrojs/vercel since your current version.


Updates @astrolib/analytics from 0.5.0 to 0.6.1

Commits

Updates @astrolib/seo from 1.0.0-beta.5 to 1.0.0-beta.8

Commits

Updates astro from 4.16.18 to 5.15.7

Release notes

Sourced from astro's releases.

[email protected]

Patch Changes

  • #14765 03fb47c Thanks @​florian-lefebvre! - Fixes a case where process.env wouldn't be properly populated during the build

  • #14690 ae7197d Thanks @​fredriknorlin! - Fixes a bug where Astro's i18n fallback system with fallbackType: 'rewrite' would not generate fallback files for pages whose filename started with a locale key.

[email protected]

Patch Changes

  • #14751 18c55e1 Thanks @​delucis! - Fixes hydration of client components when running the dev server and using a barrel file that re-exports both Astro and UI framework components.

  • #14750 35122c2 Thanks @​florian-lefebvre! - Updates the experimental Fonts API to log a warning if families with a conflicting cssVariable are provided

  • #14737 74c8852 Thanks @​Arecsu! - Fixes an error when using transition:persist with components that use declarative Shadow DOM. Astro now avoids re-attaching a shadow root if one already exists, preventing "Unable to re-attach to existing ShadowDOM" navigation errors.

  • #14750 35122c2 Thanks @​florian-lefebvre! - Updates the experimental Fonts API to allow for more granular configuration of remote font families

    A font family is defined by a combination of properties such as weights and styles (e.g. weights: [500, 600] and styles: ["normal", "bold"]), but you may want to download only certain combinations of these.

    For greater control over which font files are downloaded, you can specify the same font (ie. with the same cssVariable, name, and provider properties) multiple times with different combinations. Astro will merge the results and download only the required files. For example, it is possible to download normal 500 and 600 while downloading only italic 500:

    // astro.config.mjs
import { defineConfig, fontProviders } from 'astro/config';
export default defineConfig({
experimental: {
fonts: [
{
name: 'Roboto',
cssVariable: '--roboto',
provider: fontProviders.google(),
weights: [500, 600],
styles: ['normal'],
},
{
name: 'Roboto',
cssVariable: '--roboto',
provider: fontProviders.google(),
weights: [500],
styles: ['italic'],
},
],
},
});

[email protected]

Patch Changes

... (truncated)

Changelog

Sourced from astro's changelog.

5.15.7

Patch Changes

  • #14765 03fb47c Thanks @​florian-lefebvre! - Fixes a case where process.env wouldn't be properly populated during the build

  • #14690 ae7197d Thanks @​fredriknorlin! - Fixes a bug where Astro's i18n fallback system with fallbackType: 'rewrite' would not generate fallback files for pages whose filename started with a locale key.

5.15.6

Patch Changes

  • #14751 18c55e1 Thanks @​delucis! - Fixes hydration of client components when running the dev server and using a barrel file that re-exports both Astro and UI framework components.

  • #14750 35122c2 Thanks @​florian-lefebvre! - Updates the experimental Fonts API to log a warning if families with a conflicting cssVariable are provided

  • #14737 74c8852 Thanks @​Arecsu! - Fixes an error when using transition:persist with components that use declarative Shadow DOM. Astro now avoids re-attaching a shadow root if one already exists, preventing "Unable to re-attach to existing ShadowDOM" navigation errors.

  • #14750 35122c2 Thanks @​florian-lefebvre! - Updates the experimental Fonts API to allow for more granular configuration of remote font families

    A font family is defined by a combination of properties such as weights and styles (e.g. weights: [500, 600] and styles: ["normal", "bold"]), but you may want to download only certain combinations of these.

    For greater control over which font files are downloaded, you can specify the same font (ie. with the same cssVariable, name, and provider properties) multiple times with different combinations. Astro will merge the results and download only the required files. For example, it is possible to download normal 500 and 600 while downloading only italic 500:

    // astro.config.mjs
import { defineConfig, fontProviders } from 'astro/config';
export default defineConfig({
experimental: {
fonts: [
{
name: 'Roboto',
cssVariable: '--roboto',
provider: fontProviders.google(),
weights: [500, 600],
styles: ['normal'],
},
{
name: 'Roboto',
cssVariable: '--roboto',
provider: fontProviders.google(),
weights: [500],
styles: ['italic'],
},
],
},
});

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for astro since your current version.


Updates @astrojs/mdx from 2.1.1 to 4.3.10

Release notes

Sourced from @​astrojs/mdx's releases.

@​astrojs/mdx@​4.3.10

Patch Changes

  • #14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

@​astrojs/mdx@​4.3.9

Patch Changes

@​astrojs/mdx@​4.3.7

Patch Changes

  • Updated dependencies []:
    • @​astrojs/markdown-remark@​6.3.8

@​astrojs/mdx@​4.3.6

Patch Changes

  • Updated dependencies []:
    • @​astrojs/markdown-remark@​6.3.7

@​astrojs/mdx@​4.3.5

Patch Changes

@​astrojs/mdx@​4.3.4

Patch Changes

  • Updated dependencies []:
    • @​astrojs/markdown-remark@​6.3.6
Changelog

Sourced from @​astrojs/mdx's changelog.

4.3.10

Patch Changes

  • #14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

4.3.9

Patch Changes

4.3.8

Patch Changes

  • #14591 3e887ec Thanks @​matthewp! - Adds TypeScript support for the components prop on MDX Content component when using await render(). Developers now get proper IntelliSense and type checking when passing custom components to override default MDX element rendering.

  • #14598 7b45c65 Thanks @​delucis! - Reduces terminal text styling dependency size by switching from kleur to picocolors

4.3.7

Patch Changes

  • Updated dependencies []:
    • @​astrojs/markdown-remark@​6.3.8

4.3.6

Patch Changes

  • Updated dependencies []:
    • @​astrojs/markdown-remark@​6.3.7

4.3.5

Patch Changes

4.3.4

Patch Changes

  • Updated dependencies []:
    • @​astrojs/markdown-remark@​6.3.6

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​astrojs/mdx since your current version.


Updates @astrojs/tailwind from 5.1.0 to 5.1.5

Release notes

Sourced from @​astrojs/tailwind's releases.

@​astrojs/solid-js@​5.1.3

Patch Changes

  • #14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

@​astrojs/vue@​5.1.3

Patch Changes

  • #14715 3d55c5d Thanks @​ascorbic! - Adds support for client hydration in getContainerRenderer()

    The getContainerRenderer() function is exported by Astro framework integrations to simplify the process of rendering framework components when using the experimental Container API inside a Vite or Vitest environment. This update adds the client hydration entrypoint to the returned object, enabling client-side interactivity for components rendered using this function. Previously this required users to manually call container.addClientRenderer() with the appropriate client renderer entrypoint.

    See the container-with-vitest demo for a usage example, and the Container API documentation for more information on using framework components with the experimental Container API.

@​astrojs/solid-js@​5.1.2

Patch Changes

@​astrojs/vue@​5.1.2

Patch Changes

@​astrojs/solid-js@​5.1.1

Patch Changes

@​astrojs/vue@​5.1.1

Patch Changes

Changelog

Sourced from @​astrojs/tailwind's changelog.

5.1.5

Patch Changes

5.1.4

Patch Changes

5.1.3

Patch Changes

6.0.0-alpha.0

Patch Changes

5.1.2

Patch Changes

  • #12161 8e500f2 Thanks @​delucis! - Adds keywords to package.json to improve categorization in the Astro integrations catalog

6.0.0-alpha.0

Patch Changes

5.1.1

Patch Changes

Commits

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
Bump js-yaml, @astrojs/svelte, @astrojs/vercel, @astrolib/analytics, …
66097c5 
…@astrolib/seo, astro, @astrojs/mdx and @astrojs/tailwind

Bumps [js-yaml](https://github.com/nodeca/js-yaml), [@astrojs/svelte](https://github.com/withastro/astro/tree/HEAD/packages/integrations/svelte), [@astrojs/vercel](https://github.com/withastro/astro/tree/HEAD/packages/integrations/vercel), [@astrolib/analytics](https://github.com/onwidget/astrolib/tree/HEAD/packages/analytics), [@astrolib/seo](https://github.com/onwidget/astrolib/tree/HEAD/packages/seo), [astro](https://github.com/withastro/astro/tree/HEAD/packages/astro), [@astrojs/mdx](https://github.com/withastro/astro/tree/HEAD/packages/integrations/mdx) and [@astrojs/tailwind](https://github.com/withastro/astro/tree/HEAD/packages/integrations/tailwind). These dependencies needed to be updated together.

Updates `js-yaml` from 4.1.0 to 4.1.1
- [Changelog](https://github.com/nodeca/js-yaml/blob/master/CHANGELOG.md)
- [Commits](nodeca/js-yaml@4.1.0...4.1.1)

Updates `@astrojs/svelte` from 5.3.0 to 7.2.2
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/svelte/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/[email protected]/packages/integrations/svelte)

Updates `@astrojs/vercel` from 7.5.2 to 9.0.0
- [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/HEAD/packages/integrations/vercel)

Updates `@astrolib/analytics` from 0.5.0 to 0.6.1
- [Commits](https://github.com/onwidget/astrolib/commits/HEAD/packages/analytics)

Updates `@astrolib/seo` from 1.0.0-beta.5 to 1.0.0-beta.8
- [Commits](https://github.com/onwidget/astrolib/commits/HEAD/packages/seo)

Updates `astro` from 4.16.18 to 5.15.7
- [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/[email protected]/packages/astro)

Updates `@astrojs/mdx` from 2.1.1 to 4.3.10
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/mdx/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/[email protected]/packages/integrations/mdx)

Updates `@astrojs/tailwind` from 5.1.0 to 5.1.5
- [Release notes](https://github.com/withastro/astro/releases)
- [Changelog](https://github.com/withastro/astro/blob/main/packages/integrations/tailwind/CHANGELOG.md)
- [Commits](https://github.com/withastro/astro/commits/@astrojs/[email protected]/packages/integrations/tailwind)

---
updated-dependencies:
- dependency-name: js-yaml
  dependency-version: 4.1.1
  dependency-type: direct:development
- dependency-name: "@astrojs/svelte"
  dependency-version: 7.2.2
  dependency-type: direct:production
- dependency-name: "@astrojs/vercel"
  dependency-version: 9.0.0
  dependency-type: direct:production
- dependency-name: "@astrolib/analytics"
  dependency-version: 0.6.1
  dependency-type: direct:production
- dependency-name: "@astrolib/seo"
  dependency-version: 1.0.0-beta.8
  dependency-type: direct:production
- dependency-name: astro
  dependency-version: 5.15.7
  dependency-type: direct:production
- dependency-name: "@astrojs/mdx"
  dependency-version: 4.3.10
  dependency-type: direct:development
- dependency-name: "@astrojs/tailwind"
  dependency-version: 5.1.5
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 14, 2025
This was referenced Nov 14, 2025
Closed
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

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