Skip to content

fix(deps): update repo-tooling - #277

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/repo-tooling
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/repo-tooling

Conversation

@renovate

@renovate renovate Bot commented Sep 14, 2026

Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
@astrojs/starlight (source) 0.41.100.42.0 age confidence
@jest/globals (source) 30.5.030.5.1 age confidence
@playwright/test (source) 1.62.11.63.0 age confidence
@scalar/api-reference (source) 1.67.01.68.0 age confidence
@types/node (source) 26.4.126.5.0 age confidence
@typescript-eslint/parser (source) 8.68.08.69.0 age confidence
astro (source) 7.2.97.3.1 age confidence
baseline-browser-mapping 2.11.202.11.21 age confidence
eslint (source) 10.9.110.10.0 age confidence
eslint-plugin-react-refresh 0.5.50.5.6 age confidence
happy-dom 20.12.020.14.0 age confidence
jest (source) 30.5.030.5.1 age confidence
lucide-react-native (source) 1.40.01.42.0 age confidence
monaco-editor@0.55.1>dompurify 3.4.143.4.15 age confidence
playwright (source) 1.62.11.63.0 age confidence
pnpm (source) 12.1.0+sha512.d9b8276d97f6ec86e49815877f91ee9f63cee61f2063b304e43b6dab8fa07ce8a9afd46d2facd39f921e6a9d06b3c75a81349c7b888c2d22886bae022990103712.3.4 age confidence
postcss (source) 8.5.268.5.28 age confidence
react-native-qrcode-svg 6.3.226.3.23 age confidence
uniwind (source) 1.11.01.12.0 age confidence

Release Notes

withastro/starlight (@​astrojs/starlight)

v0.42.0

Compare Source

Minor Changes
  • #​3572 292fb17 Thanks @​HiDeoo! - Distributes package as JavaScript files with dedicated type declaration files instead of TypeScript source files.

  • #​4121 2623ae6 Thanks @​delucis! - Simplifies markup for Starlight’s mobile menu toggle

    ⚠️ Potentially breaking change: If you use a theme plugin, custom styles, or component overrides targeting the MobileMenuToggle button or PageFrame components, you may need to adjust these for the new markup. The button is no longer wrapped in a <starlight-menu-button> custom element and no longer uses the aria-expanded attribute. Instead, you can use the .sl-menu-button class name to target the button and the :popover-open pseudo-class to style the menu open state specifically.

    In the following example, custom styles for the menu button are updated for the new approach:

    - starlight-menu-button button {
    + .sl-menu-button {
      color: var(--sl-color-text);
    }
    
    - starlight-menu-button[aria-expanded='true'] button {
    + .sl-menu-button:has(~ :popover-open) {
      color: var(--sl-color-text-accent-high);
    }

    See MobileMenuToggle.astro and PageFrame.astro on GitHub for the full source code of the updated components.

  • #​3572 292fb17 Thanks @​HiDeoo! - Removes the tagline configuration option, which was never used.

    If your configuration included a tagline option, you can safely remove it without any replacement.

  • #​4134 6135f01 Thanks @​HiDeoo! - Updates internal @astrojs/mdx, @astrojs/markdown-satteri, and satteri dependencies.

    ⚠️ BREAKING CHANGE: The following minimum versions are now required:

    • astro v7.2.10 or later
    • @astrojs/markdown-satteri 0.4.0 or later (if you use it)
    • @astrojs/markdown-remark 7.3.0 or later (if you use it)

    Please update Starlight and Astro together:

    npx @astrojs/upgrade
  • #​4121 2623ae6 Thanks @​delucis! - Refactors Starlight’s mobile menu toggle to work when JavaScript fails or is disabled

    ⚠️ BREAKING CHANGE: This release drops official support for Chromium-based browsers prior to version 116 (released August 2023), Safari-based browsers prior to version 17.0 (released September 2023), and Firefox prior to version 125 (released April 2024). You can find a list of currently supported browsers and their versions using this browserslist query.

    This change also removes the data-mobile-menu-expanded attribute, which was previously added to <body> while the mobile menu is open. If you have custom code that was depending on this attribute, you will need to update it to use a new selector to check if the mobile menu is open.

    In the following example, a custom background colour for the site header while the menu is open is updated for the new approach:

    - [data-mobile-menu-expanded] header {
    + body:has(sl-sidebar-pane:popover-open) header {
      background-color: var(--sl-color-bg);
    }

v0.41.11

Compare Source

Patch Changes
  • #​4167 32a5e29 Thanks @​HiDeoo! - Fixes a layout issue and anchor links appearing for hidden headings, e.g. footnote headings, when markdown.headingLinks is enabled or the <AnchorHeading> component is used.

  • #​4148 cdfafd8 Thanks @​ematipico! - Optimizes sidebar data generation logic to speed up sites with large sidebars

jestjs/jest (@​jest/globals)

v30.5.1

Compare Source

Fixes
  • [jest-config] Don't warn about global-only options in the config that supplies the global config - the root config a project resolves to, or the first entry of --projects when no root config is passed (#​16411)
  • [jest-config, jest-types] Stop accepting reporters, coverageReporters, workerIdleMemoryLimit, cwd and runnerOptions in a project config - they were silently ignored, and now warn like the other global-only options (#​16411)
  • [jest-config, jest-validate] Warn about maxWorkers and coverageThreshold in a project config instead of dropping them without a word (#​16411)
  • [jest-resolve] Match moduleNameMapper patterns against the specifier as written again (reverting #​16390) (#​16417)
  • [jest-runtime] Resolve package imports specifiers like #dep under ESM again (#​16413)
Chore & Maintenance
  • [jest-util] Name the testEnvironmentOptions.globalsCleanup option and link the docs from the JEST-01 deprecation warning, and document the option's modes (#​16404)
microsoft/playwright (@​playwright/test)

v1.63.0

Compare Source

scalar/scalar (@​scalar/api-reference)

v1.68.0

Minor Changes
  • #​9937: Add a way to open the request body editor in the Form view by default. Set the defaultRequestBodyView: 'form' config option, or the x-scalar-default-request-body-view extension in your OpenAPI document (which also works per source). Defaults to raw, and falls back to raw when a body cannot be shown as a form.
Patch Changes
  • #​10066: Show referenced model names for array branches in schema composition selectors.
  • #​10058: chore: upgrade to Storybook 10.5.10 and drop the third-party dark mode addon
typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.69.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

withastro/astro (astro)

v7.3.1

Compare Source

Patch Changes

v7.3.0

Compare Source

Minor Changes
  • #​17767 ce7c91f Thanks @​astro-factory! - Adds --ignore-lock flag to astro preview, allowing multiple preview servers to run simultaneously on different ports. This is useful for E2E testing workflows (e.g., Playwright) that need to run several preview servers at once.

  • #​17818 c0b6581 Thanks @​florian-lefebvre! - Adds a logger parameter to image services hooks

    Custom image services now receive Astro's runtime logger as an extra argument. Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

    import type { LocalImageService } from 'astro';
    
    const service: LocalImageService = {
      // ...
      async transform(inputBuffer, transform, imageConfig, logger) {
        logger.warn(`Could not optimize "${transform.src}". Passing it through unchanged.`);
        return { data: inputBuffer, format: 'png' };
      },
    };

    Astro's built-in Sharp service now uses this logger for the warnings it emits when it encounters an unexpected or unsupported source format.

  • #​17818 c0b6581 Thanks @​florian-lefebvre! - Adds logger to the context object passed to cache providers

    Custom cache providers now receive Astro's runtime logger on the context passed to onRequest(). Messages logged with it are routed through the destination configured in logger and respect your log level, instead of being written straight to the console:

    import type { CacheProvider } from 'astro';
    
    const provider: CacheProvider = {
      name: 'my-cache',
      async onRequest({ request, url, logger }, next) {
        logger.warn(`Skipping cache for ${url.pathname} because the response sets a cookie.`);
        return next();
      },
      // ...
    };

    Astro's built-in memoryCache() provider now uses this logger for the warnings it emits when it skips caching a response that sets cookies, and when a background revalidation fails.

Patch Changes
  • #​17818 c0b6581 Thanks @​florian-lefebvre! - Updates Astro's remaining internal warnings and errors to be written through the configured logger instead of directly to the console, when possible

  • #​17886 e747cba Thanks @​matthewp! - Fixes the memory cache provider to skip responses with Vary: Cookie or Vary: *

  • #​17885 916b738 Thanks @​Princesseuh! - Improves build performance for sites with a large number of pages coming from a large amount of different modules.

  • #​17795 15e2deb Thanks @​matthewp! - Adds concurrent rendering support for experimental.incrementalBuild, including when using @astrojs/cloudflare

    Incremental builds no longer disable caching when build.concurrency is greater than 1. Projects that set build.concurrency: 1 to keep the cache enabled can remove that workaround. Cloudflare builds also reduce serialization overhead for large prerendered pages.

  • #​17879 21c34a6 Thanks @​matthewp! - Fixes missing styles, links, and scripts from content collection entries rendered inside server islands

  • #​17861 3193988 Thanks @​ethanstoner! - Fixes i18n fallback routes being generated with a corrupted path when the locale code also appears at the start of a later path segment. A page such as src/pages/en/enterprise.astro with fallback: { es: 'en' } produced the route /es/esterprise instead of /es/enterprise, so the fallback never matched the intended URL. Only the leading locale segment is rewritten now.

v7.2.10

Compare Source

Patch Changes
  • #​17262 f8e9458 Thanks @​Princesseuh! - Fixes @astrojs/markdown-remark being pinned to an exact version.

  • #​17874 10c7e63 Thanks @​astro-factory! - Fixes SSR manifest placeholder not being replaced when the server build is minified, which caused a runtime Invalid URL crash at server boot

  • #​17869 2548abf Thanks @​ematipico! - Fixes a case where the logger was improperly initialized at runtime in dev.

  • #​17878 76eff3d Thanks @​ematipico! - Fixes browser heuristic caching for cached responses that include Last-Modified or ETag validators

  • #​17833 413a6e7 Thanks @​astro-factory! - Fixes prerender conflict warnings to correctly identify the route that first rendered a duplicate pathname, instead of misattributing the conflict to an unrelated route that merely matches the URL pattern

  • #​17872 f7191cc Thanks @​jx-grxf! - Fixes Markdown images in content collections rendering an empty srcset attribute when no responsive candidates are generated.

  • #​17755 157c500 Thanks @​matthewp! - Fixes a bug where editing a content collection entry during astro dev on Windows kept serving stale content until the dev server was restarted. The data store now notifies the dev server directly after each write instead of relying only on the file watcher, which can miss the atomic rename that commits the write on some platforms.

  • Updated dependencies [f8e9458, f8e9458]:

web-platform-dx/baseline-browser-mapping (baseline-browser-mapping)

v2.11.21

Compare Source

eslint/eslint (eslint)

v10.10.0

Compare Source

ArnaudBarre/eslint-plugin-react-refresh (eslint-plugin-react-refresh)

v0.5.6

Compare Source

  • Support re-exporting namespace components (fixes #​116)
capricorn86/happy-dom (happy-dom)

v20.14.0

Compare Source

🎨 Features

v20.13.2

Compare Source

👷‍♂️ Patch fixes

v20.13.1

Compare Source

v20.13.0

Compare Source

🎨 Features

v20.12.2

Compare Source

v20.12.1

Compare Source

lucide-icons/lucide (lucide-react-native)

v1.42.0: Version 1.42.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.41.0...1.42.0

v1.41.0: Version 1.41.0

Compare Source

What's Changed

New Contributors

Full Changelog: lucide-icons/lucide@1.40.0...1.41.0

cure53/DOMPurify (monaco-editor@0.55.1>dompurify)

v3.4.15: DOMPurify 3.4.15

Compare Source

  • Added better clobbering hardening when XML content is involved, thanks @​gnyselcuk
  • Added several smaller hardening and edge-case improvements, thanks @​leechristensen
  • Bumped several dependencies where possible
pnpm/pnpm (pnpm)

v12.3.4: pnpm 12.3.4

Compare Source

Patch Changes

  • Sped up dependency resolution in large workspaces #​14352.

  • pnpm 12 now accepts the boolean settings as command-line flags on every command that takes them in pnpm 11, for example pnpm install --unsafe-perm, pnpm add foo --offline, and pnpm install --dangerously-allow-all-builds. pnpm 12 rejected them with unexpected argument, which failed every install on Vercel, whose build runs pnpm install --unsafe-perm #​14346.

    pnpm remove now accepts --unsafe-perm, the same flag pnpm install, pnpm add, and pnpm update take.

Platinum Sponsors

Bit OpenAI Notion

Gold Sponsors

Sanity Discord Vite
SerpApi CodeRabbit Stackblitz
Workleap Nx Latitude

v12.3.3: pnpm 12.3.3

Compare Source

Patch Changes

  • Fixed concurrent installs sharing a store occasionally failing with an ENOENT error while importing a package file #​14353.

  • Sped up writing the lockfile in large workspaces #​14352.

  • Sped up dependency resolution in large workspaces #​14352.

  • pnpm now runs through Node.js when it was installed by a tool that skips build scripts, such as Vercel's packageManager provisioning, Bun, Deno, or npm install --ignore-scripts. Those installs previously failed with syntax error near unexpected token ')'. They still cannot run pnpm on Windows. On macOS only a shell can start it #​14346.

Platinum Sponsors

Bit OpenAI Notion

Gold Sponsors

Sanity Discord Vite
SerpApi CodeRabbit Stackblitz
Workleap Nx Latitude

v12.3.2: pnpm 12.3.2

Compare Source

Patch Changes

  • pnpm audit --fix update no longer aborts when a vulnerable package has no safe version inside its declared range #​14508. The run updates every package it can and lists the rest as remaining.

  • pnpm install no longer reruns root lifecycle scripts when the global virtual store contains an unfinished-build marker in a package slot that the current lockfile does not use pnpm/pnpm#14485.

  • Sped up installs that have no lockfile. pnpm now links packages whose dependency subtree has no peer dependencies into the virtual store while resolution is still running.

  • pnpm run and pnpm exec now start without reinstalling on filesystems that keep sub-millisecond mtimes, such as NTFS. Previously, every run on those filesystems reinstalled first pnpm/pnpm#14486.

  • pnpm import now keeps the versions recorded in package-lock.json, npm-shrinkwrap.json, or yarn.lock when it generates pnpm-lock.yaml. A range in package.json, a catalog, or an override still decides which versions are eligible, and the recorded version is preferred among them. The generated lockfile previously could pin newer versions than the source lockfile #​14476.

    pnpm import in a workspace now imports every workspace project into the shared lockfile. It previously imported only the project in the current directory.

    pnpm import now fails with ERR_PNPM_LOCKFILE_NOT_FOUND when none of the three source lockfiles is present. It also fails with ERR_PNPM_YARN_LOCKFILE_PARSE_FAILED when it cannot parse yarn.lock. It previously generated a lockfile from scratch in both cases.

    pnpm import always resolves locally. It warns when --pnpr-server or the pnpr-server setting is given and does not use the server.

  • Sped up installs in large workspaces. Discovering the workspace projects no longer enumerates every matched directory to learn which manifest files it holds #​14352.

  • Sped up installs in large workspaces. The resolver and the peer pass allocate less for every dependency edge #​14352.

  • pnpm self-update, pnpm with, and automatic package-manager version switching no longer wait through registry retry delays when a configured registry has no signatures and registry.npmjs.org is unavailable #​14483.

  • Sped up installs in large workspaces. Saving the lockfile is faster, and the install finishes without waiting for memory cleanup #​14352.

  • pnpm install now relinks workspace packages when publishConfig.linkDirectory changes. Frozen installs report an outdated lockfile until it is regenerated pnpm/pnpm#14488.

  • The pnpm npm wrapper keeps its placeholder shebang-less so pnpm 11 can install pnpm 12 through the version store. Wrapper installs must allow lifecycle scripts to install the native binary #​14502.

  • Sped up dependency resolution when there is no lockfile, and for the dependencies a lockfile does not cover.

  • Sped up installs in large workspaces. Workspace link: targets and importer ids are now derived from the paths' suffixes under the workspace root #​14352.

  • pnpm install now reports "Already up to date" when local tarball dependencies have not changed #​14495.

  • pnpm update now accepts --ignore-scripts and skips lifecycle scripts during the update pnpm/pnpm#14512.

  • Sped up installs that restore a deleted node_modules from a warm global virtual store. pnpm no longer re-links packages that are already fully present in the global virtual store #​14510.

Platinum Sponsors

Bit 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 requested a review from simonvanlierde as a code owner September 14, 2026 01:32
@renovate
renovate Bot force-pushed the renovate/repo-tooling branch from eb9f586 to 3826d04 Compare September 14, 2026 10:49
@renovate
renovate Bot force-pushed the renovate/repo-tooling branch from 3826d04 to ec893fc Compare September 14, 2026 16:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants