Skip to content

chore(deps): update all non-major dependencies #1243

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
github-actions wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): update all non-major dependencies #1243

github-actions wants to merge 1 commit into from
+96 −131

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 1, 2025 •
edited
Loading

This PR contains the following updates:

Package Change Age Confidence
@commitlint/cli (source) 20.1.0 -> 20.2.0 age confidence
@esbuild/darwin-arm64 0.27.0 -> 0.27.1 age confidence
@playwright/test (source) 1.56.1 -> 1.57.0 age confidence
@types/express (source) 5.0.5 -> 5.0.6 age confidence
@types/node (source) 24.10.1 -> 24.10.2 age confidence
@types/react (source) 19.2.6 -> 19.2.7 age confidence
@vitejs/plugin-react (source) 5.1.1 -> 5.1.2 age confidence
@vitest/browser (source) 4.0.13 -> 4.0.15 age confidence
@vitest/browser-playwright (source) 4.0.13 -> 4.0.15 age confidence
@vitest/eslint-plugin 1.4.3 -> 1.5.2 age confidence
@vitest/ui (source) 4.0.13 -> 4.0.15 age confidence
angular-eslint (source) 21.0.1 -> 21.1.0 age confidence
daisyui (source) 5.5.5 -> 5.5.8 age confidence
eslint-plugin-jsdoc 61.4.1 -> 61.5.0 age confidence
eslint-plugin-playwright 2.3.0 -> 2.4.0 age confidence
eslint-plugin-svelte (source) 3.13.0 -> 3.13.1 age confidence
express (source) 5.1.0 -> 5.2.1 age confidence
prettier (source) 3.6.2 -> 3.7.4 age confidence
react (source) 19.2.0 -> 19.2.1 age confidence
react-dom (source) 19.2.0 -> 19.2.1 age confidence
sass 1.94.2 -> 1.95.0 age confidence
svelte (source) 5.43.14 -> 5.45.8 age confidence
typedoc (source) 0.28.14 -> 0.28.15 age confidence
typescript-eslint (source) 8.47.0 -> 8.49.0 age confidence
vite (source) 7.2.4 -> 7.2.7 age confidence
vitest (source) 4.0.13 -> 4.0.15 age confidence

Release Notes

conventional-changelog/commitlint (@​commitlint/cli)

v20.2.0

Compare Source

Note: Version bump only for package @​commitlint/cli

evanw/esbuild (@​esbuild/darwin-arm64)

v0.27.1

Compare Source

  • Fix bundler bug with var nested inside if (#​4348)

    This release fixes a bug with the bundler that happens when importing an ES module using require (which causes it to be wrapped) and there's a top-level var inside an if statement without being wrapped in a { ... } block (and a few other conditions). The bundling transform needed to hoist these var declarations outside of the lazy ES module wrapper for correctness. See the issue for details.

  • Fix minifier bug with for inside try inside label (#​4351)

    This fixes an old regression from version v0.21.4. Some code was introduced to move the label inside the try statement to address a problem with transforming labeled for await loops to avoid the await (the transformation involves converting the for await loop into a for loop and wrapping it in a try statement). However, it introduces problems for cross-compiled JVM code that uses all three of these features heavily. This release restricts this transform to only apply to for loops that esbuild itself generates internally as part of the for await transform. Here is an example of some affected code:

    // Original code
d: {
  e: {
    try {
      while (1) { break d }
    } catch { break e; }
  }
}

// Old output (with --minify)
a:try{e:for(;;)break a}catch{break e}

// New output (with --minify)
a:e:try{for(;;)break a}catch{break e}

  • Inline IIFEs containing a single expression (#​4354)

    Previously inlining of IIFEs (immediately-invoked function expressions) only worked if the body contained a single return statement. Now it should also work if the body contains a single expression statement instead:

    // Original code
const foo = () => {
  const cb = () => {
    console.log(x())
  }
  return cb()
}

// Old output (with --minify)
const foo=()=>(()=>{console.log(x())})();

// New output (with --minify)
const foo=()=>{console.log(x())};

  • The minifier now strips empty finally clauses (#​4353)

    This improvement means that finally clauses containing dead code can potentially cause the associated try statement to be removed from the output entirely in minified builds:

    // Original code
function foo(callback) {
  if (DEBUG) stack.push(callback.name);
  try {
    callback();
  } finally {
    if (DEBUG) stack.pop();
  }
}

// Old output (with --minify --define:DEBUG=false)
function foo(a){try{a()}finally{}}

// New output (with --minify --define:DEBUG=false)
function foo(a){a()}

  • Allow tree-shaking of the Symbol constructor

    With this release, calling Symbol is now considered to be side-effect free when the argument is known to be a primitive value. This means esbuild can now tree-shake module-level symbol variables:

    // Original code
const a = Symbol('foo')
const b = Symbol(bar)

// Old output (with --tree-shaking=true)
const a = Symbol("foo");
const b = Symbol(bar);

// New output (with --tree-shaking=true)
const b = Symbol(bar);
microsoft/playwright (@​playwright/test)

v1.57.0

Compare Source

Speedboard

In HTML reporter, there's a new tab we call "Speedboard":

speedboard

It shows you all your executed tests sorted by slowness,
and can help you understand where your test suite is taking longer than expected.
Take a look at yours - maybe you'll find some tests that are spending a longer time waiting than they should!

Chrome for Testing

Starting with this release, Playwright switches from Chromium, to using Chrome for Testing builds. Both headed and headless browsers are subject to this. Your tests should still be passing after upgrading to Playwright 1.57.

We're expecting no functional changes to come from this switch. The biggest change is the new icon and title in your toolbar.

new and old logo

If you still see an unexpected behaviour change, please file an issue.

On Arm64 Linux, Playwright continues to use Chromium.

Waiting for webserver output

testConfig.webServer added a wait field. Pass a regular expression, and Playwright will wait until the webserver logs match it.

import { defineConfig } from '@​playwright/test';

export default defineConfig({
  webServer: {
    command: 'npm run start',
    wait: {
      stdout: '/Listening on port (?<my_server_port>\\d+)/'
    },
  },
});

If you include a named capture group into the expression, then Playwright will provide the capture group contents via environment variables:

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

test.use({ baseUrl: `http://localhost:${process.env.MY_SERVER_PORT ?? 3000}` });

test('homepage', async ({ page }) => {
  await page.goto('/');
});

This is not just useful for capturing varying ports of dev servers. You can also use it to wait for readiness of a service that doesn't expose an HTTP readiness check, but instead prints a readiness message to stdout or stderr.

Breaking Change

After 3 years of being deprecated, we removed Page#accessibility from our API. Please use other libraries such as Axe if you need to test page accessibility. See our Node.js guide for integration with Axe.

New APIs

  • New property testConfig.tag adds a tag to all tests in this run. This is useful when using merge-reports.
  • worker.on('console') event is emitted when JavaScript within the worker calls one of console API methods, e.g. console.log or console.dir. worker.waitForEvent() can be used to wait for it.
  • locator.description() returns locator description previously set with locator.describe(), and Locator.toString() now uses the description when available.
  • New option steps in locator.click() and locator.dragTo() that configures the number of mousemove events emitted while moving the mouse pointer to the target element.
  • Network requests issued by Service Workers are now reported and can be routed through the BrowserContext, only in Chromium. You can opt out using the PLAYWRIGHT_DISABLE_SERVICE_WORKER_NETWORK environment variable.
  • Console messages from Service Workers are dispatched through worker.on('console'). You can opt out of this using the PLAYWRIGHT_DISABLE_SERVICE_WORKER_CONSOLE environment variable.

Browser Versions

  • Chromium 143.0.7499.4
  • Mozilla Firefox 144.0.2
  • WebKit 26.0
vitejs/vite-plugin-react (@​vitejs/plugin-react)

v5.1.2

Compare Source

vitest-dev/vitest (@​vitest/browser)

v4.0.15

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.0.14

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub
vitest-dev/eslint-plugin-vitest (@​vitest/eslint-plugin)

v1.5.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.1

Compare Source

   🐞 Bug Fixes
  • no-alias-methods: Align no-alias-methods rule with Vitest by aliasing toThrow to toThrowError  -  by @​y-hsgw in #​832 (4ea56)
    View changes on GitHub

v1.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
  • consistent-test-it: Handle aliased Vitest imports when enforcing consistent test names  -  by @​y-hsgw in #​828 (54be6)
    View changes on GitHub

What's Changed

  • fix(consistent-test-it): Handle aliased Vitest imports when enforcing consistent test names by @​y-hsgw in #​828
  • feat: Add rule to recommended Vitest ESLint config by @​y-hsgw in #​827

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.4.4...v1.5.0

v1.4.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

What's Changed

New Contributors

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.4.3...v1.4.4

angular-eslint/angular-eslint (angular-eslint)

v21.1.0

Compare Source

🚀 Features
  • eslint-plugin: add prefer-signal-model rule to encourage using model() for two-way bindings (#​2818)
🩹 Fixes
❤️ Thank You
saadeghi/daisyui (daisyui)

v5.5.8

Compare Source

Bug Fixes
  • badge padding to respect --size-selector, clean up kbd and tab padding properties. closes: #​4293 (e713958)

v5.5.7

Compare Source

Bug Fixes

v5.5.6

Compare Source

Bug Fixes
gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)

v61.5.0

Compare Source

Features
  • check-tag-names, require-template, check-template-names: make typeParam a non-preferred alias for template (3cd7cbd)

v61.4.2

Compare Source

Bug Fixes
  • require-rejects: reflect proper tag name in error message (44b2631)
playwright-community/eslint-plugin-playwright (eslint-plugin-playwright)

v2.4.0

Compare Source

Bug Fixes
  • missing-playwright-await: prevent infinite recursion in checkValidity (9ce346d)
Features
sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v3.13.1

Compare Source

Patch Changes
expressjs/express (express)

v5.2.1

Compare Source

=======================

v5.2.0

Compare Source

========================

  • Security fix for CVE-2024-51999 (GHSA-pj86-cfqh-vqx6)
  • deps: body-parser@^2.2.1
  • A deprecation warning was added when using res.redirect with undefined arguments, Express now emits a warning to help detect calls that pass undefined as the status or URL and make them easier to fix.
prettier/prettier (prettier)

v3.7.4

Compare Source

diff

LWC: Avoid quote around interpolations (#​18383 by @​kovsu)
<!-- Input -->
<div foo={bar}>   </div>

<!-- Prettier 3.7.3 (--embedded-language-formatting off) -->
<div foo="{bar}"></div>

<!-- Prettier 3.7.4 (--embedded-language-formatting off) -->
<div foo={bar}></div>
TypeScript: Fix comment inside union type gets duplicated (#​18393 by @​fisker)
// Input
type Foo = (/** comment */ a | b) | c;

// Prettier 3.7.3
type Foo = /** comment */ (/** comment */ a | b) | c;

// Prettier 3.7.4
type Foo = /** comment */ (a | b) | c;
TypeScript: Fix unstable comment print in union type comments (#​18395 by @​fisker)
// Input
type X = (A | B) & (
  // comment
  A | B
);

// Prettier 3.7.3 (first format)
type X = (A | B) &
  (// comment
  A | B);

// Prettier 3.7.3 (second format)
type X = (
  | A
  | B // comment
) &
  (A | B);

// Prettier 3.7.4
type X = (A | B) &
  // comment
  (A | B);

v3.7.3

Compare Source

diff

API: Fix prettier.getFileInfo() change that breaks VSCode extension (#​18375 by @​fisker)

An internal refactor accidentally broke the VSCode extension plugin loading.

v3.7.2

Compare Source

diff

JavaScript: Fix string print when switching quotes (#​18351 by @​fisker)
// Input
console.log("A descriptor\\'s .kind must be \"method\" or \"field\".")

// Prettier 3.7.1
console.log('A descriptor\\'s .kind must be "method" or "field".');

// Prettier 3.7.2
console.log('A descriptor\\\'s .kind must be "method" or "field".');
JavaScript: Preserve quote for embedded HTML attribute values (#​18352 by @​kovsu)
// Input
const html = /* HTML */ ` <div class="${styles.banner}"></div> `;

// Prettier 3.7.1
const html = /* HTML */ ` <div class=${styles.banner}></div> `;

// Prettier 3.7.2
const html = /* HTML */ ` <div class="${styles.banner}"></div> `;
TypeScript: Fix comment in empty type literal (#​18364 by @​fisker)
// Input
export type XXX = {
  // tbd
};

// Prettier 3.7.1
export type XXX = { // tbd };

// Prettier 3.7.2
export type XXX = {
  // tbd
};

v3.7.1

Compare Source

diff

API: Fix performance regression in doc printer (#​18342 by @​fisker)

Prettier 3.7.0 can be very slow when formatting big files, the regression has been fixed.

v3.7.0

Compare Source

diff

🔗 Release Notes

facebook/react (react)

v19.2.1

Compare Source

React Server Components
sass/dart-sass (sass)

v1.95.0

Compare Source

  • Add support for the CSS-style if() function. In addition to supporting the
    plain CSS syntax, this also supports a sass() query that takes a Sass
    expression that evaluates to true or false at preprocessing time depending
    on whether the Sass value is truthy. If there are no plain-CSS queries, the
    function will return the first value whose query returns true during
    preprocessing. For example, if(sass(false): 1; sass(true): 2; else: 3)
    returns 2.

  • The old Sass if() syntax is now deprecated. Users are encouraged to migrate
    to the new CSS syntax. if($condition, $if-true, $if-false) can be changed to
    if(sass($condition): $if-true; else: $if-false).

    See the Sass website for details.

  • Plain-CSS if() functions are now considered "special numbers", meaning that
    they can be used in place of arguments to CSS color functions.

  • Plain-CSS if() functions and attr() functions are now considered "special
    variable strings" (like var()), meaning they can now be used in place of
    multiple arguments or syntax fragments in various CSS functions.

v1.94.3

Compare Source

  • Fix the span reported for standalone % expressions followed by whitespace.
sveltejs/svelte (svelte)

v5.45.8

Compare Source

Patch Changes

  • fix: set AST root.start to 0 and root.end to template.length (#​17125)

  • fix: prevent erroneous state_referenced_locally warnings on prop fallbacks (#​17329)

v5.45.7

Compare Source

Patch Changes

  • fix: Add <textarea wrap="off"> as a valid attribute value (#​17326)

  • fix: add more css selectors to print() (#​17330)

  • fix: don't crash on hydratable serialization failure (#​17315)

v5.45.6

Compare Source

Patch Changes

  • fix: don't issue a11y warning for <video> without captions if it has no src (#​17311)

  • fix: add srcObject to permitted <audio>/<video> attributes (#​17310)

v5.45.5

Compare Source

Patch Changes

  • fix: correctly reconcile each blocks after outroing branches are resumed (#​17258)

  • fix: destroy each items after siblings are resumed (#​17258)

v5.45.4

Compare Source

Patch Changes

  • chore: move DOM-related effect properties to effect.nodes (#​17293)

  • fix: allow $props.id() to occur after an await (#​17285)

  • fix: keep reactions up to date even when read outside of effect (#​17295)

v5.45.3

Compare Source

Patch Changes

  • add props to state_referenced_locally (#​17266)

  • fix: preserve node locations for better sourcemaps (#​17269)

  • fix: handle cross-realm Promises in hydratable (#​17284)

v5.45.2

Compare Source

Patch Changes

  • fix: array destructuring after await (#​17254)

  • fix: throw on invalid {@&#8203;tag}s (#​17256)

v5.45.1

Compare Source

Patch Changes
  • fix: link offscreen items and last effect in each block correctly (#​17240)

v5.45.0

Compare Source

Minor Changes

v5.44.1

Compare Source

Patch Changes

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 04:59 AM, on day 1 of the month ( * 0-4 1 * * ) (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 has been generated by Renovate Bot.

@github-actions
Copy link
Contributor Author

github-actions bot commented Dec 1, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @vitest/[email protected]
npm error Found: @vitest/[email protected]
npm error node_modules/@vitest/browser
npm error   dev @vitest/browser@"^4.0.0" from the root project
npm error   @vitest/browser@"4.0.15" from @vitest/[email protected]
npm error   node_modules/@vitest/browser-playwright
npm error     dev @vitest/browser-playwright@"^4.0.12" from the root project
npm error     peerOptional @vitest/browser-playwright@"4.0.15" from [email protected]
npm error     node_modules/vitest
npm error       dev vitest@"^4.0.0" from the root project
npm error       5 more (@angular/build, @vitest/browser, ...)
npm error
npm error Could not resolve dependency:
npm error peerOptional @vitest/browser@"4.0.13" from @vitest/[email protected]
npm error node_modules/@vitest/coverage-v8
npm error   dev @vitest/coverage-v8@"^4.0.0" from @agnos-ui/[email protected]
npm error   eslint-plugin
npm error     @agnos-ui/[email protected]
npm error     node_modules/@agnos-ui/eslint-plugin
npm error       workspace eslint-plugin from the root project
npm error
npm error Conflicting peer dependency: @vitest/[email protected]
npm error node_modules/@vitest/browser
npm error   peerOptional @vitest/browser@"4.0.13" from @vitest/[email protected]
npm error   node_modules/@vitest/coverage-v8
npm error     dev @vitest/coverage-v8@"^4.0.0" from @agnos-ui/[email protected]
npm error     eslint-plugin
npm error       @agnos-ui/[email protected]
npm error       node_modules/@agnos-ui/eslint-plugin
npm error         workspace eslint-plugin from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-12-09T01_10_57_767Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-12-09T01_10_57_767Z-debug-0.log

@github-actions github-actions bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 9bd5ad9 to 017660e Compare December 8, 2025 03:19
@github-actions github-actions bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 5e4270c to 53cf62a Compare December 8, 2025 20:19
@github-actions github-actions bot force-pushed the renovate/all-minor-patch branch from 53cf62a to fadb6dc Compare December 8, 2025 23:16
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

renovate

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant