Skip to content

fix(deps): update all non-major dependencies#356

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all-minor-patch
Open

fix(deps): update all non-major dependencies#356
renovate[bot] wants to merge 1 commit intomainfrom
renovate/all-minor-patch

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 24, 2025 •
edited
Loading

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@astrojs/check (source) 0.9.4 → 0.9.8 age confidence dependencies patch
@astrojs/netlify (source) 6.5.13 → 6.6.5 age confidence dependencies minor
@astrojs/starlight (source) ^0.36.0 → ^0.38.0 age confidence dependencies minor
@astrojs/svelte (source) 7.2.0 → 7.2.5 age confidence dependencies patch
@eslint/js (source) 9.37.0 → 9.39.4 age confidence devDependencies minor
@playwright/test (source) 1.56.1 → 1.58.2 age confidence devDependencies minor
@sveltejs/adapter-auto (source) 7.0.0 → 7.0.1 age confidence devDependencies patch
@sveltejs/package (source) 2.5.4 → 2.5.7 age confidence devDependencies patch
@sveltejs/vite-plugin-svelte (source) 6.2.1 → 6.2.4 age confidence devDependencies patch
@sveltejs/vite-plugin-svelte (source) 6.2.1 → 6.2.4 age confidence dependencies patch
@testing-library/svelte (source) 5.2.8 → 5.3.1 age confidence devDependencies minor
@types/node (source) 22.18.11 → 22.19.15 age confidence devDependencies minor
acorn 8.15.0 → 8.16.0 age confidence dependencies minor
eslint (source) 9.37.0 → 9.39.4 age confidence devDependencies minor
eslint-plugin-playwright 2.2.2 → 2.10.1 age confidence devDependencies minor
eslint-plugin-svelte (source) 3.12.4 → 3.16.0 age confidence devDependencies minor
esrap 2.1.0 → 2.2.4 age confidence dependencies minor
execa 9.6.0 → 9.6.1 age confidence devDependencies patch
globals 16.4.0 → 16.5.0 age confidence devDependencies minor
happy-dom 20.0.4 → 20.8.7 age confidence devDependencies minor
node (source) 24.10.0 → 24.14.0 age confidence volta minor
pnpm (source) 10.18.3 → 10.32.1 age confidence packageManager minor
pnpm (source) 10.18.3 → 10.32.1 age confidence volta minor
prettier (source) 3.6.2 → 3.8.1 age confidence devDependencies minor
prettier-plugin-svelte 3.4.0 → 3.5.1 age confidence devDependencies minor
publint (source) 0.3.14 → 0.3.18 age confidence devDependencies patch
release-plan 0.17.2 → 0.17.4 age confidence devDependencies patch
sharp (source, changelog) 0.34.4 → 0.34.5 age confidence dependencies patch
svelte-check 4.3.3 → 4.4.5 age confidence devDependencies minor
typescript-eslint (source) 8.46.1 → 8.57.2 age confidence devDependencies minor

Release Notes

withastro/astro (@​astrojs/check)

v0.9.8

Compare Source

Patch Changes

v0.9.7

Compare Source

Patch Changes

v0.9.6

Patch Changes

v0.9.5

Patch Changes
  • d415d4e: When no errors or warnings are detected, display "0 errors" or "0 warnings" in a dimmed color on the console instead of red or yellow.
withastro/astro (@​astrojs/netlify)

v6.6.5

Compare Source

Patch Changes

v6.6.4

Compare Source

Patch Changes

v6.6.3

Compare Source

Patch Changes

v6.6.2

Compare Source

Patch Changes

v6.6.1

Compare Source

Patch Changes

v6.6.0

Compare Source

Minor Changes

  • #​14543 9b3241d Thanks @​matthewp! - Enables Netlify's skew protection feature for Astro sites deployed on Netlify. 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.

    When you deploy to Netlify, the deployment ID is now automatically included in both asset requests and API calls, allowing Netlify to serve the correct version to every user. These are set for built-in features (Actions, View Transitions, Server Islands, Prefetch). If you are making your own fetch requests to your site, you can include the header manually using the DEPLOY_ID environment variable:

    const response = await fetch('/api/endpoint', {
  headers: {
    'X-Netlify-Deploy-ID': import.meta.env.DEPLOY_ID,
  },
});
Patch Changes
withastro/starlight (@​astrojs/starlight)

v0.38.2

Compare Source

Patch Changes

  • #​3759 f24ce99 Thanks @​MilesChou! - Fixes an issue where monolingual sites using a region-specific locale (e.g., zh-TW) as the default would incorrectly display base language translations (e.g., zh Simplified Chinese) instead of the region-specific ones (e.g., zh-TW Traditional Chinese).

  • #​3768 a4c6c20 Thanks @​delucis! - Improves performance of sidebar generation for sites with very large sidebars

v0.38.1

Compare Source

Patch Changes

v0.38.0

Compare Source

Minor Changes
Upgrade Astro and dependencies

⚠️ BREAKING CHANGE: Astro v5 is no longer supported. Make sure you update Astro and any other official integrations at the same time as updating Starlight:

npx @​astrojs/upgrade

Community Starlight plugins and Astro integrations may also need to be manually updated to work with Astro v6. If you encounter any issues, please reach out to the plugin or integration author to see if it is a known issue or if an updated version is being worked on.

Update your collections

⚠️ BREAKING CHANGE: Drops support for content collections backwards compatibility.

In Astro 5.x, projects could delay upgrading to the new Content Layer API introduced for content collections because of some existing automatic backwards compatibility that was not previously behind a flag. This meant that it was possible to upgrade from Astro 4 to Astro 5 without updating your content collections, even if you had not enabled the legacy.collections flag. Projects would continue to build, and no errors or warnings would be displayed.

Astro v6.0 now removes this automatic legacy content collections support, along with the legacy.collections flag.

If you experience content collections errors after updating to v6, check your project for any removed legacy features that may need updating to the Content Layer API. See the Starlight v0.30.0 upgrade guide for detailed instructions on upgrading legacy collections to the new Content Layer API.

If you are unable to make any changes to your collections at this time, including Starlight's default docs and i18n collections, you can enable the legacy.collectionsBackwardsCompat flag to upgrade to v6 without updating your collections. This temporary flag preserves some legacy v4 content collections features, and will allow you to keep your collections in their current state until the legacy flag is no longer supported.

  • #​3704 375edcc Thanks @​florian-lefebvre! - Fixes autocomplete for components exported from @astrojs/starlight/components/*

    ⚠️ Potentially breaking change: This change moves some files used in Starlight’s component internals out of the components/ directory. Direct use of these files was not and is not officially supported. If you previously imported TableOfContents/starlight-toc.ts, TableOfContents/TableOfContentsList.astro, Icons.ts, or SidebarPersistState.ts, please review your code when updating.

  • #​3729 3642625 Thanks @​delucis! - Improves Starlight’s default body font stack to better support languages such as Chinese, Japanese, and Korean on Windows.
    For most users there should be no visible change.

    If you would prefer to keep the previous font stack, you can add the following custom CSS to your site:

    :root {
  --sl-font-system: ui-sans-serif, system-ui, 'Segoe UI', Roboto,
    'Helvetica Neue', Arial, 'Noto Sans', sans-serif, 'Apple Color Emoji',
    'Segoe UI Emoji', 'Segoe UI Symbol', 'Noto Color Emoji';
}

  • #​3598 fff38d5 Thanks @​HiDeoo! - Makes hover styles consistent in Starlight’s navigation bar

    Previously, the social icon links and language/theme switchers in Starlight’s navigation bar, dimmed on hover.
    After this change, they now increase in contrast on hover instead.
    This matches hover behavior elsewhere, for example in the sidebar, table of contents, or search button.

    ⚠️ Potentially breaking change: this is a subtle change to the hover style colors.
    If you want to preserve the previous styling, you can add the following custom CSS to your site:

    starlight-theme-select label,
starlight-lang-select label {
  color: var(--sl-color-gray-1);

  &:hover {
    color: var(--sl-color-white);
  }
}

.social-icons a:hover {
  color: var(--sl-color-text-accent);
  opacity: 0.66;
}

v0.37.7

Compare Source

Patch Changes
  • #​3726 8a09b60 Thanks @​delucis! - Fixes an issue using components containing scripts inside Starlight’s steps component in versions of Astro >= 5.16.9

v0.37.6

Compare Source

Patch Changes

v0.37.5

Compare Source

Patch Changes

v0.37.4

Compare Source

Patch Changes

  • #​3534 703fab0 Thanks @​HiDeoo! - Fixes support for running builds when npx is unavailable.

    Previously, Starlight would spawn a process to run the Pagefind search indexing binary using npx. On platforms where npx isn’t available, this could cause issues. Starlight now runs Pagefind using its Node.js API to avoid a separate process. As a side effect, you may notice that logging during builds is now less verbose.

  • #​3656 a0e6368 Thanks @​delucis! - Fixes several edge cases in highlighting the current page heading in Starlight’s table of contents

  • #​3663 00cbf00 Thanks @​lines-of-codes! - Adds Thai language support

  • #​3658 ac79329 Thanks @​delucis! - Avoids adding redundant aria-current="false" attributes to sidebar entries

  • #​3382 db295c2 Thanks @​trueberryless! - Fixes an issue where the mobile table of contents is unable to find the first heading when a page has a tall banner.

v0.37.3

Compare Source

Patch Changes

v0.37.2

Compare Source

Patch Changes

v0.37.1

Compare Source

Patch Changes
  • #​3603 30f6e7f Thanks @​delucis! - Fixes support for providing an absolute URL to Starlight’s favicon configuration option

v0.37.0

Compare Source

Minor Changes

  • #​3491 28810f0 Thanks @​JusticeMatthew! - Changes text overflow styling in Markdown content

    ⚠️ Potentially breaking change: This release switches the overflow-wrap CSS style for common elements to break-word. In most cases, there should be little visual impact, but this change can impact how layouts with implicit sizing (such as tables) look, improving legibility in how words wrap.

    If you want to preserve the previous styling, you can add the following custom CSS to your site:

    p,
h1,
h2,
h3,
h4,
h5,
h6,
code {
  overflow-wrap: anywhere;
}

  • #​3351 239698c Thanks @​HiDeoo! - Ensures that Starlight CSS layer order is predictable in custom pages using the <StarlightPage> component.

    Previously, due to how import order works in Astro, the <StarlightPage> component had to be the first import in custom pages to set up cascade layers used internally by Starlight to manage the order of its styles.

    With this change, this restriction no longer applies and Starlight’s styles will be applied correctly regardless of the import order of the <StarlightPage> component.

  • #​3521 ca7b771 Thanks @​shubham-padia! - Fixes an issue where a vertical scrollbar could be displayed on the Starlight <Tabs> component when zooming the page

    ⚠️ Potentially breaking change: The <Tabs> component no longer uses margin-bottom and border-bottom to highlight the current tab. This is now done with a box-shadow. If you have custom styling for your tabs, you may need to update it.

    If you want to preserve the previous styling, you can add the following custom CSS to your site:

    starlight-tabs .tab {
  margin-bottom: -2px;
}

starlight-tabs .tab > [role='tab'] {
  border-bottom: 2px solid var(--sl-color-gray-5);
  box-shadow: none;
}

starlight-tabs .tab [role='tab'][aria-selected='true'] {
  border-color: var(--sl-color-text-accent);
}

  • #​3549 1cf50eb Thanks @​jacobdalamb! - Updates the default sans-serif system font stack, dropping support for the -apple-system and BlinkMacSystemFont font names used in older browsers. These are no longer needed in browsers officially supported by Starlight.

    If you still need to support older browsers, you can add the following custom CSS to your site:

    :root {
  --sl-font-system: ui-sans-serif, system-ui, -apple-system,
    BlinkMacSystemFont, 'Segoe UI', Roboto, 'Helvetica Neue', Arial,
    'Noto Sans', sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji',
    'Segoe UI Symbol', 'Noto Color Emoji';
}

  • #​3332 f61f99d Thanks @​HiDeoo! - Adds a new markdown.processedDirs configuration option to specify additional directories where files should be processed by Starlight’s Markdown pipeline.

    By default, Starlight’s processing only applies to Markdown and MDX content loaded using Starlight’s docsLoader(). This new option allows to extend this processing to other directories, which can be useful if you are rendering content from a custom content collection using the <StarlightPage> component and expect Starlight’s Markdown processing to be applied to that content as well.

v0.36.3

Compare Source

Patch Changes

  • #​3555 547dc30 Thanks @​Its-Just-Nans! - Improves the error message thrown when using a file in the public/ directory with Starlight’s customCss configuration option

  • #​3496 b78fda4 Thanks @​delucis! - Fixes invalid <head> output when configuration is missing:

    • Omits <meta property="og:description" /> if Starlight’s description option is unset
    • Omits <link rel="canonical" /> and <meta property="og:url" /> if Astro’s site option is unset

  • #​3511 8727df1 Thanks @​astrobot-houston! - Updates the seti:gitlab icon to match latest version from Seti UI Icons

v0.36.2

Compare Source

Patch Changes
withastro/astro (@​astrojs/svelte)

v7.2.5

Compare Source

Patch Changes

v7.2.4

Compare Source

Patch Changes
  • #​15004 16f3994 Thanks @​antonyfaris! - Fixes an issue where Svelte components used in Astro files would incorrectly report type errors when using client:* directives.

v7.2.3

Compare Source

Patch Changes
  • #​14934 4264a36 Thanks @​antonyfaris! - Fixes an issue where Svelte 5 components used in Astro files would not have proper type checking and IntelliSense.

v7.2.2

Compare Source

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.

v7.2.1

Compare Source

Patch Changes
eslint/eslint (@​eslint/js)

v9.39.4

Compare Source

v9.39.3

Compare Source

Bug Fixes

  • 791bf8d fix: restore TypeScript 4.0 compatibility in types (#​20504) (sethamus)

Chores

v9.39.2

Compare Source

v9.39.1

Compare Source

v9.39.0

Compare Source

v9.38.0

Compare Source

Features
  • ce40f74 feat: update complexity rule to only highlight function header (#​20048) (Atul Nair)
  • e37e590 feat: correct no-loss-of-precision false positives with e notation (#​20187) (Francesco Trotta)
Bug Fixes
  • 50c3dfd fix: improve type support for isolated dependencies in pnpm (#​20201) (Francesco Trotta)
  • a1f06a3 fix: correct SourceCode typings (#​20114) (Pixel998)
Documentation
  • 462675a docs: improve web accessibility by hiding non-semantic character (#​20205) (루밀LuMir)
  • c070e65 docs: correct formatting in no-irregular-whitespace rule documentation (#​20203) (루밀LuMir)
  • b39e71a docs: Update README (GitHub Actions Bot)
  • cd39983 docs: move custom-formatters type descriptions to nodejs-api (#​20190) (Percy Ma)
Chores
microsoft/playwright (@​playwright/test)

v1.58.2

Compare Source

v1.58.1

Compare Source

Highlights

#​39036 fix(msedge): fix local network permissions
#​39037 chore: update cft download location
#​38995 chore(webkit): disable frame sessions on fronzen builds

Browser Versions
  • Chromium 145.0.7632.6
  • Mozilla Firefox 146.0.1
  • WebKit 26.0

v1.58.0

Compare Source

v1.57.0

Compare Source

sveltejs/kit (@​sveltejs/adapter-auto)

v7.0.1

Compare Source

Patch Changes
  • feat: update adapter-netlify to version 6 (77ab341)
sveltejs/kit (@​sveltejs/package)

v2.5.7

Compare Source

Patch Changes
  • chore(deps): update dependency chokidar to v5 (#​14986)

v2.5.6

Compare Source

Patch Changes
  • fix: transform .ts extensions to .js in import/export statements of Svelte files when using rewriteRelativeImportExtensions (#​14936)

v2.5.5

Compare Source

Patch Changes
  • fix: resolve aliases before transpiling for rewriteRelativeImportExtensions (#​14673)
sveltejs/vite-plugin-svelte (@​sveltejs/vite-plugin-svelte)

v6.2.4

Compare Source

Patch Changes
  • fix(hmr): ensure that svelte files are recompiled and updated css modules returned correctly when reported out of order (#​1258)

v6.2.3

Compare Source

Patch Changes
  • fix(filter): ignore zero-tagged ids per rollup convention (#​1255)

[v6.2.2](https://redirect.github.com/sveltejs/vite-plugin

Configuration

📅 Schedule: Branch creation - "before 7am on friday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added the internal label Oct 24, 2025
@netlify
Copy link

netlify bot commented Oct 24, 2025 •
edited
Loading

❌ Deploy Preview for sheepdog failed. Why did it fail? →

Name Link
🔨 Latest commit e09f17b
🔍 Latest deploy log https://app.netlify.com/projects/sheepdog/deploys/69c1ed33c4cfa800085d1ce6

@pkg-pr-new
Copy link

pkg-pr-new bot commented Oct 24, 2025 •
edited
Loading 

npm i https://pkg.pr.new/@sheepdog/core@356

npm i https://pkg.pr.new/@sheepdog/svelte@356

npm i https://pkg.pr.new/@sheepdog/vanilla@356

commit: e09f17b

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 16 times, most recently from 0f95d8e to e1044c5 Compare October 31, 2025 19:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 7 times, most recently from 17b5ad4 to 306ba68 Compare November 6, 2025 19:50
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 37a9ab2 to 733c711 Compare November 11, 2025 03:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 14 times, most recently from d728ea0 to b7d1398 Compare November 27, 2025 15:43
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 5b80850 to 3d03d2a Compare November 28, 2025 17:56
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Nov 28, 2025
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 10 times, most recently from 2958f31 to 1aa1eac Compare December 5, 2025 05:08
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 9c0044f to 74ba1d3 Compare December 8, 2025 18:09
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

internal

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants