Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Oct 21, 2025

Note: This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update
@changesets/changelog-github (source) ^0.5.1^0.5.2 age confidence devDependencies patch
@changesets/cli (source) ^2.29.7^2.29.8 age confidence devDependencies patch
@sanity/pkg-utils (source) ^8.1.21^8.1.29 age confidence devDependencies patch
@sanity/prettier-config ^2.0.1^2.0.3 age confidence devDependencies patch
@sanity/ui (source) 4.0.0-static.384.0.0-static.46 age confidence devDependencies patch
@types/cpx (source) ^1.5.5^1.5.6 age confidence devDependencies patch
@types/express (source) ^5.0.3^5.0.6 age confidence devDependencies patch
@types/lodash (source) ^4.17.20^4.17.23 age confidence devDependencies patch
@types/node (source) ^20.19.21^20.19.30 age confidence devDependencies patch
@types/react (source) ^19.2.2^19.2.8 age confidence devDependencies patch
@types/react-dom (source) ^19.2.2^19.2.3 age confidence devDependencies patch
@vanilla-extract/css (source) ^1.17.4^1.18.0 age confidence dependencies minor
@vanilla-extract/vite-plugin (source) ^5.1.1^5.1.4 age confidence dependencies patch
@vitejs/plugin-react (source) ^5.0.4^5.1.2 age confidence dependencies minor
axe-core (source) ^4.11.0^4.11.1 age confidence dependencies patch
esbuild ^0.25.11^0.27.2 age confidence dependencies minor
eslint-plugin-prettier ^5.5.4^5.5.5 age confidence devDependencies patch
express (source) ^5.1.0^5.2.1 age confidence dependencies minor
peter-evans/create-pull-request (changelog) 271a8d022a9089 action digest
prettier (source) ^3.6.2^3.8.0 age confidence devDependencies minor
react (source) ^19.2.0^19.2.3 age confidence devDependencies patch
react-dom (source) ^19.2.0^19.2.3 age confidence devDependencies patch
react-is (source) ^19.2.0^19.2.3 age confidence devDependencies patch
vite (source) ^7.1.10^7.3.1 age confidence dependencies minor

Release Notes

changesets/changesets (@​changesets/changelog-github)

v0.5.2

Compare Source

sanity-io/pkg-utils (@​sanity/pkg-utils)

v8.1.29

Compare Source

Bug Fixes

v8.1.28

Compare Source

Bug Fixes

v8.1.27

Compare Source

Bug Fixes

v8.1.26

Compare Source

Bug Fixes

v8.1.25

Compare Source

Bug Fixes

v8.1.24

Compare Source

Bug Fixes

v8.1.23

Compare Source

Bug Fixes

v8.1.22

Compare Source

Bug Fixes
sanity-io/prettier-config (@​sanity/prettier-config)

v2.0.3

Compare Source

Bug Fixes

v2.0.2

Compare Source

Bug Fixes
sanity-io/ui (@​sanity/ui)

v4.0.0-static.46

Compare Source

Bug Fixes
  • revert "<Activity> on <Tooltip> & <Popover>" (2d7050f)
Reverts
  • Revert "chore: fix test suite" (c2a03d6)

This release is also available on:

v4.0.0-static.45

Compare Source

Features
  • use <Activity> on <Tooltip> & <Popover> (a20335f)

This release is also available on:

v4.0.0-static.44

Compare Source

Bug Fixes
  • use native useEffectEvent (e75f30b)

This release is also available on:

v4.0.0-static.43

Compare Source

Bug Fixes
  • button: revert adding explicity inline-size (b2aba01)

This release is also available on:

v4.0.0-static.42

Compare Source

Bug Fixes
  • deps: replace framer-motion with motion/react (9a95ffd)

This release is also available on:

v4.0.0-static.41

Compare Source

Bug Fixes
  • toast: clear existing timeout id when pushing toast (97b3a5f)

This release is also available on:

v4.0.0-static.40

Compare Source

Bug Fixes
  • toast: support duration: Infinity (d6f7c61)

This release is also available on:

v4.0.0-static.39

Compare Source

Bug Fixes
  • css: increase contrast of placeholder text (2673e0a)

This release is also available on:

vanilla-extract-css/vanilla-extract (@​vanilla-extract/css)

v1.18.0

Compare Source

Minor Changes
  • #​1566 8b49b35 Thanks @​lfantone! - style: Add support for @starting-style rules

    EXAMPLE USAGE:

    import { style } from '@&#8203;vanilla-extact/css';
    export const styleWithStartingStyle = style({
      backgroundColor: 'black',
      '@&#8203;starting-style': {
        backgroundColor: 'white'
      }
    });
Patch Changes
  • #​1646 0b2c09e Thanks @​plesiecki! - Swap the order of createVar's overloads to enable inference of VarDelcaration type

  • #​1666 c6047fb Thanks @​askoufis! - Remove custom container properties type

    The csstype package used by Vanilla Extract now provides types for container properties, so the custom type definitions that were previously necessary have been removed.

v1.17.5

Compare Source

Patch Changes
vanilla-extract-css/vanilla-extract (@​vanilla-extract/vite-plugin)

v5.1.4

Compare Source

Patch Changes

v5.1.3

Compare Source

Patch Changes

v5.1.2

Compare Source

Patch Changes
vitejs/vite-plugin-react (@​vitejs/plugin-react)

v5.1.2

Compare Source

v5.1.1

Compare Source

Update code to support newer rolldown-vite (#​976)

rolldown-vite will remove optimizeDeps.rollupOptions in favor of optimizeDeps.rolldownOptions soon. This plugin now uses optimizeDeps.rolldownOptions to support newer rolldown-vite. Please update rolldown-vite to the latest version if you are using an older version.

v5.1.0

Compare Source

Add @vitejs/plugin-react/preamble virtual module for SSR HMR (#​890)

SSR applications can now initialize HMR runtime by importing @vitejs/plugin-react/preamble at the top of their client entry instead of manually calling transformIndexHtml. This simplifies SSR setup for applications that don't use the transformIndexHtml API.

Fix raw Rolldown support for Rolldown 1.0.0-beta.44+ (#​930)

Rolldown 1.0.0-beta.44+ removed the top-level jsx option in favor of transform.jsx. This plugin now uses the transform.jsx option to support Rolldown 1.0.0-beta.44+.

dequelabs/axe-core (axe-core)

v4.11.1

Compare Source

evanw/esbuild (esbuild)

v0.27.2

Compare Source

  • Allow import path specifiers starting with #/ (#​4361)

    Previously the specification for package.json disallowed import path specifiers starting with #/, but this restriction has recently been relaxed and support for it is being added across the JavaScript ecosystem. One use case is using it for a wildcard pattern such as mapping #/* to ./src/* (previously you had to use another character such as #_* instead, which was more confusing). There is some more context in nodejs/node#49182.

    This change was contributed by @​hybrist.

  • Automatically add the -webkit-mask prefix (#​4357, #​4358)

    This release automatically adds the -webkit- vendor prefix for the mask CSS shorthand property:

    /* Original code */
    main {
      mask: url(x.png) center/5rem no-repeat
    }
    
    /* Old output (with --target=chrome110) */
    main {
      mask: url(x.png) center/5rem no-repeat;
    }
    
    /* New output (with --target=chrome110) */
    main {
      -webkit-mask: url(x.png) center/5rem no-repeat;
      mask: url(x.png) center/5rem no-repeat;
    }

    This change was contributed by @​BPJEnnova.

  • Additional minification of switch statements (#​4176, #​4359)

    This release contains additional minification patterns for reducing switch statements. Here is an example:

    // Original code
    switch (x) {
      case 0:
        foo()
        break
      case 1:
      default:
        bar()
    }
    
    // Old output (with --minify)
    switch(x){case 0:foo();break;case 1:default:bar()}
    
    // New output (with --minify)
    x===0?foo():bar();
  • Forbid using declarations inside switch clauses (#​4323)

    This is a rare change to remove something that was previously possible. The Explicit Resource Management proposal introduced using declarations. These were previously allowed inside case and default clauses in switch statements. This had well-defined semantics and was already widely implemented (by V8, SpiderMonkey, TypeScript, esbuild, and others). However, it was considered to be too confusing because of how scope works in switch statements, so it has been removed from the specification. This edge case will now be a syntax error. See tc39/proposal-explicit-resource-management#215 and rbuckton/ecma262#14 for details.

    Here is an example of code that is no longer allowed:

    switch (mode) {
      case 'read':
        using readLock = db.read()
        return readAll(readLock)
    
      case 'write':
        using writeLock = db.write()
        return writeAll(writeLock)
    }

    That code will now have to be modified to look like this instead (note the additional { and } block statements around each case body):

    switch (mode) {
      case 'read': {
        using readLock = db.read()
        return readAll(readLock)
      }
      case 'write': {
        using writeLock = db.write()
        return writeAll(writeLock)
      }
    }

    This is not being released in one of esbuild's breaking change releases since this feature hasn't been finalized yet, and esbuild always tracks the current state of the specification (so esbuild's previous behavior was arguably incorrect).

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);

v0.27.0

Compare Source

This release deliberately contains backwards-incompatible changes. To avoid automatically picking up releases like this, you should either be pinning the exact version of esbuild in your package.json file (recommended) or be using a version range syntax that only accepts patch upgrades such as ^0.26.0 or ~0.26.0. See npm's documentation about semver for more information.

  • Use Uint8Array.fromBase64 if available (#​4286)

    With this release, esbuild's binary loader will now use the new Uint8Array.fromBase64 function unless it's unavailable in the configured target environment. If it's unavailable, esbuild's previous code for this will be used as a fallback. Note that this means you may now need to specify target when using this feature with Node (for example --target=node22) unless you're using Node v25+.

  • Update the Go compiler from v1.23.12 to v1.25.4 (#​4208, #​4311)

    This raises the operating system requirements for running esbuild:

    • Linux: now requires a kernel version of 3.2 or later
    • macOS: now requires macOS 12 (Monterey) or later

v0.26.0

Compare Source

  • Enable trusted publishing (#​4281)

    GitHub and npm are recommending that maintainers for packages such as esbuild switch to trusted publishing. With this release, a VM on GitHub will now build and publish all of esbuild's packages to npm instead of me. In theory.

    Unfortunately there isn't really a way to test that this works other than to do it live. So this release is that live test. Hopefully this release is uneventful and is exactly the same as the previous one (well, except for the green provenance attestation checkmark on npm that happens with trusted publishing).

v0.25.12

Compare Source

  • Fix a minification regression with CSS media queries (#​4315)

    The previous release introduced support for parsing media queries which unintentionally introduced a regression with the removal of duplicate media rules during minification. Specifically the grammar for @media <media-type> and <media-condition-without-or> { ... } was missing an equality check for the <media-condition-without-or> part, so rules with different suffix clauses in this position would incorrectly compare equal and be deduplicated. This release fixes the regression.

  • Update the list of known JavaScript globals (#​4310)

    This release updates esbuild's internal list of known JavaScript globals. These are globals that are known to not have side-effects when the property is accessed. For example, accessing the global Array property is considered to be side-effect free but accessing the global scrollY property can trigger a layout, which is a side-effect. This is used by esbuild's tree-shaking to safely remove unused code that is known to be side-effect free. This update adds the following global properties:

    From ES2017:

    • Atomics
    • SharedArrayBuffer

    From ES2020:

    • BigInt64Array
    • BigUint64Array

    From ES2021:

    • FinalizationRegistry
    • WeakRef

    From ES2025:

    • Float16Array
    • Iterator

    Note that this does not indicate that constructing any of these objects is side-effect free, just that accessing the identifier is side-effect free. For example, this now allows esbuild to tree-shake classes that extend from Iterator:

    // This can now be tree-shaken by esbuild:
    class ExampleIterator extends Iterator {}
  • Add support for the new @view-transition CSS rule (#​4313)

    With this release, esbuild now has improved support for pretty-printing and minifying the new @view-transition rule (which esbuild was previously unaware of):

    /* Original code */
    @&#8203;view-transition {
      navigation: auto;
      types: check;
    }
    
    /* Old output */
    @&#8203;view-transition { navigation: auto; types: check; }
    
    /* New output */
    @&#8203;view-transition {
      navigation: auto;
      types: check;
    }

    The new view transition feature provides a mechanism for creating animated transitions between documents in a multi-page app. You can read more about view transition rules here.

    This change was contributed by @​yisibl.

  • Trim CSS rules that will never match

    The CSS minifier will now remove rules whose selectors contain :is() and :where() as those selectors will never match. These selectors can currently be automatically generated by esbuild when you give esbuild nonsensical input such as the following:

    /* Original code */
    div:before {
      color: green;
      &.foo {
        color: red;
      }
    }
    
    /* Old output (with --supported:nesting=false --minify) */
    div:before{color:green}:is().foo{color:red}
    
    /* New output (with --supported:nesting=false --minify) */
    div:before{color:green}

    This input is nonsensical because CSS nesting is (unfortunately) not supported inside of pseudo-elements such as :before. Currently esbuild generates a rule containing :is() in this case when you tell esbuild to transform nested CSS into non-nested CSS. I think it's reasonable to do that as it sort of helps explain what's going on (or at least indicates that something is wrong in the output). It shouldn't be present in minified code, however, so this release now strips it out.

prettier/eslint-plugin-prettier (eslint-plugin-prettier)

v5.5.5

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.8.0

Compare Source

diff

🔗 Release note

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.1 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.3: 19.2.3 (December 11th, 2025)

Compare Source

React Server Components

v19.2.2: 19.2.2 (December 11th, 2025)

Compare Source

React Server Components

v19.2.1: 19.2.1 (December 3rd, 2025)

Compare Source

React Server Components
vitejs/vite (vite)

v7.3.1

Compare Source

Please refer to CHANGELOG.md for details.

v7.3.0

Compare Source

Please refer to CHANGELOG.md for details.

v7.2.7

Compare Source

v7.2.6

Compare Source

7.2.6 (2025-12-01)

v7.2.4

Compare Source

Bug Fixes

v7.2.3

[Compare Source](https://redirect.github.com/vitejs/vite/compare/v7.2.2...


Configuration

📅 Schedule: Branch creation - "before 3am on the first day of the month" (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 Mend Renovate using a curated preset maintained by Sanity. View repository job log here

@renovate renovate bot requested a review from a team October 21, 2025 15:44
@vercel
Copy link

vercel bot commented Oct 21, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
ui-workshop Ready Ready Preview, Comment Jan 18, 2026 2:40am

Request Review

@changeset-bot
Copy link

changeset-bot bot commented Oct 21, 2025

⚠️ No Changeset found

Latest commit: d5d8bc4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@socket-security
Copy link

socket-security bot commented Oct 21, 2025

@renovate renovate bot force-pushed the renovate/static-non-major branch from f117945 to b359b1d Compare October 22, 2025 03:39
@renovate renovate bot force-pushed the renovate/static-non-major branch from b359b1d to 5dc28de Compare October 23, 2025 06:28
@renovate renovate bot force-pushed the renovate/static-non-major branch from 5dc28de to 4769150 Compare October 23, 2025 15:49
@renovate renovate bot force-pushed the renovate/static-non-major branch from 4769150 to cdfdbbc Compare October 24, 2025 03:46
@renovate renovate bot force-pushed the renovate/static-non-major branch from cdfdbbc to aecf1d8 Compare October 26, 2025 07:05
@renovate renovate bot force-pushed the renovate/static-non-major branch from aecf1d8 to 8487480 Compare October 26, 2025 23:08
@renovate renovate bot force-pushed the renovate/static-non-major branch from 8487480 to 4de221d Compare October 27, 2025 07:12
@renovate renovate bot force-pushed the renovate/static-non-major branch from 4de221d to 5cf372c Compare October 27, 2025 12:19
@renovate renovate bot force-pushed the renovate/static-non-major branch from 5cf372c to 6231f21 Compare October 29, 2025 22:49
@renovate renovate bot force-pushed the renovate/static-non-major branch from 6231f21 to 88253ca Compare October 30, 2025 23:12
@renovate renovate bot force-pushed the renovate/static-non-major branch from 88253ca to d0ca623 Compare October 31, 2025 13:52
@renovate renovate bot force-pushed the renovate/static-non-major branch from d0ca623 to 60b2f12 Compare October 31, 2025 21:43
@renovate renovate bot force-pushed the renovate/static-non-major branch from 0f51478 to 387e509 Compare December 15, 2025 15:45
@renovate renovate bot force-pushed the renovate/static-non-major branch from 387e509 to cde00c7 Compare December 18, 2025 10:55
@renovate renovate bot force-pushed the renovate/static-non-major branch from cde00c7 to 980a96b Compare December 19, 2025 11:10
@renovate renovate bot force-pushed the renovate/static-non-major branch from 980a96b to 2b10088 Compare December 20, 2025 03:37
@renovate renovate bot force-pushed the renovate/static-non-major branch from 2b10088 to d42452c Compare December 31, 2025 19:11
@renovate renovate bot force-pushed the renovate/static-non-major branch from d42452c to a884caa Compare January 8, 2026 20:53
@renovate renovate bot force-pushed the renovate/static-non-major branch from a884caa to cd57516 Compare January 9, 2026 22:28
@renovate renovate bot force-pushed the renovate/static-non-major branch from cd57516 to b4d50bc Compare January 10, 2026 02:15
@renovate renovate bot force-pushed the renovate/static-non-major branch from b4d50bc to 82a71d3 Compare January 10, 2026 10:05
@renovate renovate bot force-pushed the renovate/static-non-major branch from 82a71d3 to 6e925e7 Compare January 10, 2026 14:03
@renovate renovate bot force-pushed the renovate/static-non-major branch from 6e925e7 to 77ad84a Compare January 13, 2026 18:55
@renovate renovate bot force-pushed the renovate/static-non-major branch from 77ad84a to bb91cde Compare January 15, 2026 19:06
@renovate renovate bot force-pushed the renovate/static-non-major branch from bb91cde to be0c83e Compare January 17, 2026 13:56
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