Skip to content

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

Merged
paoloricciuti merged 3 commits into
mainfrom
renovate/all-minor-patch
Jul 11, 2025
Merged

fix(deps): update all non-major dependencies#334
paoloricciuti merged 3 commits into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Jul 4, 2025 •
edited
Loading

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence Type Update
@astrojs/netlify (source) 6.3.4 -> 6.4.1 age confidence dependencies minor
@astrojs/starlight (source) 0.34.3 -> 0.34.4 age confidence dependencies patch
@eslint/js (source) 9.29.0 -> 9.30.1 age confidence devDependencies minor
@fontsource/calistoga (source) 5.2.5 -> 5.2.6 age confidence dependencies patch
@fontsource/pt-sans (source) 5.2.5 -> 5.2.6 age confidence dependencies patch
@playwright/test (source) 1.52.0 -> 1.54.0 age confidence devDependencies minor
@sveltejs/kit (source) 2.21.1 -> 2.22.5 age confidence devDependencies minor
@sveltejs/package (source) 2.3.11 -> 2.3.12 age confidence devDependencies patch
@types/node (source) 22.15.21 -> 22.16.3 age confidence devDependencies minor
@vitest/coverage-v8 (source) 3.1.4 -> 3.2.4 age confidence devDependencies minor
@vitest/ui (source) 3.1.4 -> 3.2.4 age confidence devDependencies minor
acorn 8.14.1 -> 8.15.0 age confidence dependencies minor
astro (source) 5.8.0 -> 5.11.0 age confidence dependencies minor
eslint (source) 9.27.0 -> 9.30.1 age confidence devDependencies minor
eslint-plugin-svelte (source) 3.9.3 -> 3.10.1 age confidence devDependencies minor
esrap 1.4.6 -> 1.4.9 age confidence dependencies patch
execa 9.5.3 -> 9.6.0 age confidence devDependencies minor
globals 16.1.0 -> 16.3.0 age confidence devDependencies minor
globals 16.2.0 -> 16.3.0 age confidence devDependencies minor
happy-dom 18.0.0 -> 18.0.1 age confidence devDependencies patch
node (source) 22.16.0 -> 22.17.0 age confidence volta minor
pnpm (source) 10.12.1 -> 10.13.1 age confidence packageManager minor
pnpm (source) 10.12.1 -> 10.13.1 age confidence volta minor
prettier (source) 3.5.3 -> 3.6.2 age confidence devDependencies minor
sharp (source, changelog) 0.34.2 -> 0.34.3 age confidence dependencies patch
svelte (source) 5.33.1 -> 5.35.6 age confidence devDependencies minor
svelte (source) 5.33.1 -> 5.35.6 age confidence dependencies minor
svelte-check 4.2.1 -> 4.2.2 age confidence devDependencies patch
typescript-eslint (source) 8.32.1 -> 8.36.0 age confidence devDependencies minor
typescript-eslint (source) 8.34.1 -> 8.36.0 age confidence devDependencies minor
vite (source) 7.0.0 -> 7.0.4 age confidence devDependencies patch
vitest (source) 3.1.4 -> 3.2.4 age confidence devDependencies minor

Release Notes

withastro/astro (@​astrojs/netlify)

v6.4.1

Compare Source

Patch Changes

v6.4.0

Compare Source

Minor Changes

  • #​13952 de82ef2 Thanks @​ematipico! - Adds support for the experimental static headers Astro feature.

    When the feature is enabled via option experimentalStaticHeaders, and experimental Content Security Policy is enabled, the adapter will generate Response headers for static pages, which allows support for CSP directives that are not supported inside a <meta> tag (e.g. frame-ancestors).

    import { defineConfig } from 'astro/config';
import netlify from '@&#8203;astrojs/netlify';

export default defineConfig({
  adapter: netlify({
    experimentalStaticHeaders: true,
  }),
  experimental: {
    cps: true,
  },
});
Patch Changes
withastro/starlight (@​astrojs/starlight)

v0.34.4

Compare Source

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

v9.30.1

Compare Source

v9.30.0

Compare Source

fontsource/font-files (@​fontsource/calistoga)

v5.2.6

Compare Source

fontsource/font-files (@​fontsource/pt-sans)

v5.2.6

Compare Source

microsoft/playwright (@​playwright/test)

v1.54.0

Compare Source

Highlights

  • New cookie property partitionKey in browserContext.cookies() and browserContext.addCookies(). This property allows to save and restore partitioned cookies. See CHIPS MDN article for more information. Note that browsers have different support and defaults for cookie partitioning.

  • New option noSnippets to disable code snippets in the html report.

    import { defineConfig } from '@&#8203;playwright/test';

export default defineConfig({
  reporter: [['html', { noSnippets: true }]]
});

  • New property location in test annotations, for example in testResult.annotations and testInfo.annotations. It shows where the annotation like test.skip or test.fixme was added.

Command Line

  • New option --user-data-dir in multiple commands. You can specify the same user data dir to reuse browsing state, like authentication, between sessions.

    npx playwright codegen --user-data-dir=./user-data

  • Option -gv has been removed from the npx playwright test command. Use --grep-invert instead.

  • npx playwright open does not open the test recorder anymore. Use npx playwright codegen instead.

Miscellaneous

  • Support for Node.js 16 has been removed.
  • Support for Node.js 18 has been deprecated, and will be removed in the future.

Browser Versions

  • Chromium 139.0.7258.5
  • Mozilla Firefox 140.0.2
  • WebKit 26.0

This version was also tested against the following stable channels:

  • Google Chrome 140
  • Microsoft Edge 140

v1.53.2

Compare Source

v1.53.1

Compare Source

v1.53.0

Compare Source

Trace Viewer and HTML Reporter Updates

  • New Steps in Trace Viewer and HTML reporter: New Trace Viewer Steps

  • New option in 'html' reporter to set the title of a specific test run:

    import { defineConfig } from '@&#8203;playwright/test';

export default defineConfig({
  reporter: [['html', { title: 'Custom test run #&#8203;1028' }]]
});

Miscellaneous

  • New option kind in testInfo.snapshotPath() controls which snapshot path template is used.

  • New method locator.describe() to describe a locator. Used for trace viewer and reports.

    const button = page.getByTestId('btn-sub').describe('Subscribe button');
await button.click();

  • npx playwright install --list will now list all installed browsers, versions and locations.

Browser Versions

  • Chromium 138.0.7204.4
  • Mozilla Firefox 139.0
  • WebKit 18.5

This version was also tested against the following stable channels:

  • Google Chrome 137
  • Microsoft Edge 137
sveltejs/kit (@​sveltejs/kit)

v2.22.5

Compare Source

Patch Changes
  • fix: re-add @sveltejs/kit to optimizeDeps.exclude (#​13983)

v2.22.4

Compare Source

Patch Changes
  • fix: force $app/* modules to be bundled (#​13977)

v2.22.3

Compare Source

Patch Changes
  • fix: don't bundle @sveltejs/kit (#​13971)

v2.22.2

Compare Source

Patch Changes

  • fix: use fallback if untrack doesn't exist in svelte package (#​13933)

  • fix: warning for chrome devtools requests now suggests sv instead of vite plugin (#​13905)

v2.22.1

Compare Source

Patch Changes

  • fix: prevent infinite loop when calling pushState/replaceState in $effect (#​13914)

  • chore: use manualChunks to bundle single and inline apps with Rolldown (#​13915)

v2.22.0

Compare Source

Minor Changes
  • feat: add support for Vite 7 and Rolldown. See https://vite.dev/guide/rolldown.html#how-to-try-rolldown for details about how to try experimental Rolldown support. You will also need vite-plugin-svelte@^6.0.0-next.0 and vite@^7.0.0-beta.0. Compilation should be faster using Rolldown, but with larger bundle sizes until additional tree-shaking is implemented in Rolldown. See #​13738 for ongoing work. (#​13747)

v2.21.5

Compare Source

Patch Changes

  • fix: correctly set the sequential focus navigation point when using hash routing (#​13884)

  • fix: regression when resetting focus and the URL hash contains selector combinators or separators (#​13884)

v2.21.4

Compare Source

Patch Changes
  • fix: correctly access transport decoders on the client when building for a single or inline output app (#​13871)

v2.21.3

Compare Source

Patch Changes

  • fix: correctly invalidate static analysis cache of child nodes when modifying a universal +layout file during dev (#​13793)

  • fix: correctly set sequential focus navigation starting point after navigation (#​10856)

  • fix: suppress console spam for chrome devtools requests (#​13830)

  • fix: avoid externalising packages that depend on @sveltejs/kit so that libraries can also use redirect and error helpers (#​13843)

  • fix: correctly run deserialize on the server (#​13686)

  • fix: correctly inline stylesheets of components dynamically imported in a universal load function if they are below the configured inlineStyleThreshold (#​13723)

v2.21.2

Compare Source

Patch Changes
  • fix: omit stack when logging 404 errors (#​13848)
sveltejs/kit (@​sveltejs/package)

v2.3.12

Compare Source

Patch Changes
  • fix: handle non-semver-style dependency versions (#​13925)
vitest-dev/vitest (@​vitest/coverage-v8)

v3.2.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.3

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.2

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v3.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v3.2.0

Compare Source

acornjs/acorn (acorn)

v8.15.0

Compare Source

withastro/astro (astro)

v5.11.0

Compare Source

Minor Changes

  • #​13972 db8f8be Thanks @​ematipico! - Updates the NodeApp.match() function in the Adapter API to accept a second, optional parameter to allow adapter authors to add headers to static, prerendered pages.

    NodeApp.match(request) currently checks whether there is a route that matches the given Request. If there is a prerendered route, the function returns undefined, because static routes are already rendered and their headers cannot be updated.

    When the new, optional boolean parameter is passed (e.g. NodeApp.match(request, true)), Astro will return the first matched route, even when it's a prerendered route. This allows your adapter to now access static routes and provides the opportunity to set headers for these pages, for example, to implement a Content Security Policy (CSP).

Patch Changes

  • #​14029 42562f9 Thanks @​ematipico! - Fixes a bug where server islands wouldn't be correctly rendered when they are rendered inside fragments.

    Now the following examples work as expected:

v5.10.2

Compare Source

Patch Changes

  • #​14000 3cbedae Thanks @​feelixe! - Fix routePattern JSDoc examples to show correct return values

  • #​13990 de6cfd6 Thanks @​isVivek99! - Fixes a case where astro:config/client and astro:config/server virtual modules would not contain config passed to integrations updateConfig() during the build

  • #​14019 a160d1e Thanks @​ascorbic! - Removes the requirement to set type: 'live' when defining experimental live content collections

    Previously, live collections required a type and loader configured. Now, Astro can determine that your collection is a live collection without defining it explicitly.

    This means it is now safe to remove type: 'live' from your collections defined in src/live.config.ts:

    import { defineLiveCollection } from 'astro:content';
import { storeLoader } from '@&#8203;mystore/astro-loader';

const products = defineLiveCollection({
-  type: 'live',
  loader: storeLoader({
    apiKey: process.env.STORE_API_KEY,
    endpoint: 'https://api.mystore.com/v1',
  }),
});

export const collections = { products };

    This is not a breaking change: your existing live collections will continue to work even if you still include type: 'live'. However, we suggest removing this line at your earliest convenience for future compatibility when the feature becomes stable and this config option may be removed entirely.

  • #​13966 598da21 Thanks @​msamoylov! - Fixes a broken link on the default 404 page in development

v5.10.1

Compare Source

Patch Changes

  • #​13988 609044c Thanks @​ascorbic! - Fixes a bug in live collections that caused it to incorrectly complain about the collection being defined in the wrong file

  • #​13909 b258d86 Thanks @​isVivek99! - Fixes rendering of special boolean attributes for custom elements

  • #​13983 e718375 Thanks @​florian-lefebvre! - Fixes a case where the toolbar audit would incorrectly flag images processed by Astro in content collections documents

  • #​13999 f077b68 Thanks @​ascorbic! - Adds lastModified field to experimental live collection cache hints

    Live loaders can now set a lastModified field in the cache hints for entries and collections to indicate when the data was last modified. This is then available in the cacheHint field returned by getCollection and getEntry.

  • #​13987 08f34b1 Thanks @​ematipico! - Adds an informative message in dev mode when the CSP feature is enabled.

  • #​14005 82aad62 Thanks @​ematipico! - Fixes a bug where inline styles and scripts didn't work when CSP was enabled. Now when adding <styles> elements inside an Astro component, their hashes care correctly computed.

  • #​13985 0b4c641 Thanks @​jsparkdev! - Updates wrong link

v5.10.0

Compare Source

Minor Changes

  • #​13917 e615216 Thanks @​ascorbic! - Adds a new priority attribute for Astro's image components.

    This change introduces a new priority option for the <Image /> and <Picture /> components, which automatically sets the loading, decoding, and fetchpriority attributes to their optimal values for above-the-fold images which should be loaded immediately.

    It is a boolean prop, and you can use the shorthand syntax by simply adding priority as a prop to the <Image /> or <Picture /> component. When set, it will apply the following attributes:

    • loading="eager"
    • decoding="sync"
    • fetchpriority="high"

    The individual attributes can still be set manually if you need to customize your images further.

    By default, the Astro <Image /> component generates <img> tags that lazy-load their content by setting loading="lazy" and decoding="async". This improves performance by deferring the loading of images that are not immediately visible in the viewport, and gives the best scores in performance audits like Lighthouse.

    The new priority attribute will override those defaults and automatically add the best settings for your high-priority assets.

    This option was previously available for experimental responsive images, but now it is a standard feature for all images.

Usage
<Image src="/path/to/image.jpg" alt="An example image" priority />

[!Note]
You should only use the priority option for images that are critical to the initial rendering of the page, and ideally only one image per page. This is often an image identified as the LCP element when running Lighthouse tests. Using it for too many images will lead to performance issues, as it forces the browser to load those images immediately, potentially blocking the rendering of other content.

  • #​13917 e615216 Thanks @​ascorbic! - The responsive images feature introduced behind a flag in v5.0.0 is no longer experimental and is available for general use.

    The new responsive images feature in Astro automatically generates optimized images for different screen sizes and resolutions, and applies the correct attributes to ensure that images are displayed correctly on all devices.

    Enable the image.responsiveStyles option in your Astro config. Then, set a layout attribute on any or component, or configure a default image.layout, for instantly responsive images with automatically generated srcset and sizes attributes based on the image's dimensions and the layout type.

    Displaying images correctly on the web can be challenging, and is one of the most common performance issues seen in sites. This new feature simplifies the most challenging part of the process: serving your site visitor an image optimized for their viewing experience, and for your website's performance.

    For full details, see the updated Image guide.

Migration from Experimental Responsive Images

The experimental.responsiveImages flag has been removed, and all experimental image configuration options have been renamed to their final names.

If you were using the experimental responsive images feature, you'll need to update your configuration:

Remove the experimental flag
export default defineConfig({
   experimental: {
-    responsiveImages: true,
   },
});
Update image configuration options

During the experimental phase, default styles were applied automatically to responsive images. Now, you need to explicitly set the responsiveStyles option to true if you want these styles applied.

export default defineConfig({
  image: {
+    responsiveStyles: true,
  },
});

The experimental image configuration options have been renamed:

Before:

export default defineConfig({
  image: {
    experimentalLayout: 'constrained',
    experimentalObjectFit: 'cover',
    experimentalObjectPosition: 'center',
    experimentalBreakpoints: [640, 750, 828, 1080, 1280],
    experimentalDefaultStyles: true,
  },
  experimental: {
    responsiveImages: true,
  },
});

After:

export default defineConfig({
  image: {
    layout: 'constrained',
    objectFit: 'cover',
    objectPosition: 'center',
    breakpoints: [640, 750, 828, 1080, 1280],
    responsiveStyles: true, // This is now *false* by default
  },
});
Component usage remains the same

The layout, fit, and position props on <Image> and <Picture> components work exactly the same as before:

<Image
  src={myImage}
  alt="A responsive image"
  layout="constrained"
  fit="cover"
  position="center"
/>

If you weren't using the experimental responsive images feature, no changes are required.

Please see the Image guide for more information on using responsive images in Astro.

  • #​13685 3c04c1f Thanks @​ascorbic! - Adds experimental support for live content collections

    Live content collections are a new type of content collection that fetch their data at runtime rather than build time. This allows you to access frequently-updated data from CMSs, APIs, databases, or other sources using a unified API, without needing to rebuild your site when the data changes.

Live collections vs build-time collections

In Astro 5.0, the content layer API added support for adding diverse content sources to content collections. You can create loaders that fetch data from any source at build time, and then access it inside a page via getEntry() and getCollection(). The data is cached between builds, giving fast access and updates.

However there is no method for updating the data store between builds, meaning any updates to the d

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 Jul 4, 2025
@netlify

netlify Bot commented Jul 4, 2025 •
edited
Loading

Copy link
Copy Markdown

✅ Deploy Preview for sheepdog ready!

Name Link
🔨 Latest commit b12d39d
🔍 Latest deploy log https://app.netlify.com/projects/sheepdog/deploys/6870f352e754b800083c6e74
😎 Deploy Preview https://deploy-preview-334--sheepdog.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@pkg-pr-new

pkg-pr-new Bot commented Jul 4, 2025 •
edited
Loading

Copy link
Copy Markdown 
npm i https://pkg.pr.new/@sheepdog/core@334

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

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

commit: 5c24b03

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from b49f0ed to 5dc82fe Compare July 11, 2025 10:33
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 5dc82fe to 0de892b Compare July 11, 2025 10:37
@paoloricciuti
paoloricciuti merged commit 6faca53 into main Jul 11, 2025
12 checks passed
@paoloricciuti
paoloricciuti deleted the renovate/all-minor-patch branch July 11, 2025 11:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@paoloricciuti paoloricciuti paoloricciuti approved these changes

Assignees

No one assigned

Labels

internal

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@paoloricciuti