fix(deps): update all non-major dependencies by renovate[bot] · Pull Request #619 · adelsz/pgtyped

renovate · 2025-08-01T07:31:05Z

This PR contains the following updates:

Package	Change	Age	Confidence
@types/node (source)	`22.10.5` → `22.19.15`
@types/node (source)	`22.13.14` → `22.19.15`
@types/pg (source)	`8.11.14` → `8.20.0`
esbuild	`^0.25.0` → `^0.27.0`
pg (source)	`8.14.1` → `8.20.0`
react (source)	`19.1.1` → `19.2.4`
react-dom (source)	`19.1.1` → `19.2.4`
ts-jest (source)	`29.3.4` → `29.4.6`

Release Notes

evanw/esbuild (esbuild)

`v0.27.4`

Compare Source

Fix a regression with CSS media queries (#4395, #4405, #4406)

Version 0.25.11 of esbuild introduced support for parsing media queries. This unintentionally introduced a regression with printing media queries that use the <media-type> and <media-condition-without-or> grammar. Specifically, esbuild was failing to wrap an or clause with parentheses when inside <media-condition-without-or>. This release fixes the regression.

Here is an example:
```
/* Original code */
@&#8203;media only screen and ((min-width: 10px) or (min-height: 10px)) {
  a { color: red }
}

/* Old output (incorrect) */
@&#8203;media only screen and (min-width: 10px) or (min-height: 10px) {
  a {
    color: red;
  }
}

/* New output (correct) */
@&#8203;media only screen and ((min-width: 10px) or (min-height: 10px)) {
  a {
    color: red;
  }
}
```
Fix an edge case with the inject feature (#4407)

This release fixes an edge case where esbuild's inject feature could not be used with arbitrary module namespace names exported using an export {} from statement with bundling disabled and a target environment where arbitrary module namespace names is unsupported.

With the fix, the following inject file:
```
import jquery from 'jquery';
export { jquery as 'window.jQuery' };
```
Can now always be rewritten as this without esbuild sometimes incorrectly generating an error:
```
export { default as 'window.jQuery' } from 'jquery';
```
Attempt to improve API handling of huge metafiles (#4329, #4415)

This release contains a few changes that attempt to improve the behavior of esbuild's JavaScript API with huge metafiles (esbuild's name for the build metadata, formatted as a JSON object). The JavaScript API is designed to return the metafile JSON as a JavaScript object in memory, which makes it easy to access from within a JavaScript-based plugin. Multiple people have encountered issues where this API breaks down with a pathologically-large metafile.

The primary issue is that V8 has an implementation-specific maximum string length, so using the JSON.parse API with large enough strings is impossible. This release will now attempt to use a fallback JavaScript-based JSON parser that operates directly on the UTF8-encoded JSON bytes instead of using JSON.parse when the JSON metafile is too big to fit in a JavaScript string. The new fallback path has not yet been heavily-tested. The metafile will also now be generated with whitespace removed if the bundle is significantly large, which will reduce the size of the metafile JSON slightly.

However, hitting this case is potentially a sign that something else is wrong. Ideally you wouldn't be building something so enormous that the build metadata can't even fit inside a JavaScript string. You may want to consider optimizing your project, or breaking up your project into multiple parts that are built independently. Another option could potentially be to use esbuild's command-line API instead of its JavaScript API, which is more efficient (although of course then you can't use JavaScript plugins, so it may not be an option).

`v0.27.3`

Compare Source

Preserve URL fragments in data URLs (#4370)

Consider the following HTML, CSS, and SVG:

index.html:

<!DOCTYPE html>
<html>
  <head><link rel="stylesheet" href="icons.css"></head>
  <body><div class="triangle"></div></body>
</html>

icons.css:

.triangle {
  width: 10px;
  height: 10px;
  background: currentColor;
  clip-path: url(./triangle.svg#x);
}

triangle.svg:

<svg xmlns="http://www.w3.org/2000/svg">
  <defs>
    <clipPath id="x">
      <path d="M0 0H10V10Z"/>
    </clipPath>
  </defs>
</svg>

The CSS uses a URL fragment (the #x) to reference the clipPath element in the SVG file. Previously esbuild's CSS bundler didn't preserve the URL fragment when bundling the SVG using the dataurl loader, which broke the bundled CSS. With this release, esbuild will now preserve the URL fragment in the bundled CSS:

/* icons.css */
.triangle {
  width: 10px;
  height: 10px;
  background: currentColor;
  clip-path: url('data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg"><defs><clipPath id="x"><path d="M0 0H10V10Z"/></clipPath></defs></svg>#x');
}

Parse and print CSS @scope rules (#4322)

This release includes dedicated support for parsing @scope rules in CSS. These rules include optional "start" and "end" selector lists. One important consequence of this is that the local/global status of names in selector lists is now respected, which improves the correctness of esbuild's support for CSS modules. Minification of selectors inside @scope rules has also improved slightly.

Here's an example:
```
/* Original code */
@&#8203;scope (:global(.foo)) to (:local(.bar)) {
  .bar {
    color: red;
  }
}

/* Old output (with --loader=local-css --minify) */
@&#8203;scope (:global(.foo)) to (:local(.bar)){.o{color:red}}

/* New output (with --loader=local-css --minify) */
@&#8203;scope(.foo)to (.o){.o{color:red}}
```
Fix a minification bug with lowering of for await (#4378, #4385)

This release fixes a bug where the minifier would incorrectly strip the variable in the automatically-generated catch clause of lowered for await loops. The code that generated the loop previously failed to mark the internal variable references as used.
Update the Go compiler from v1.25.5 to v1.25.7 (#4383, #4388)

This PR was contributed by @MikeWillCook.

`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).

brianc/node-postgres (pg)

`v8.20.0`

Compare Source

Add onConnect callback to pg.Pool constructor options allowing for async initialization of newly created & connected pooled clients.

`v8.19.0`

Compare Source

Deprecate interal query queue.
Pass connection parameters to password callback.

`v8.18.0`

Compare Source

Return the client instance as the result of calling connect (previously it was void).

Throw correct error if database URL parsing fails.

`v8.16.3`

Compare Source

`v8.16.2`

Compare Source

`v8.16.1`

Compare Source

`v8.16.0`

Compare Source

Add support for min connection pool size.

`v8.15.6`

Compare Source

`v8.15.5`

Compare Source

`v8.15.2`

Compare Source

`v8.15.1`

Compare Source

`v8.15.0`

Compare Source

Add support for esm importing. CommonJS importing is still also supported.

facebook/react (react)

`v19.2.4`: 19.2.4 (January 26th, 2026)

Compare Source

React Server Components

Add more DoS mitigations to Server Actions, and harden Server Components (#35632 by @gnoff, @lubieowoce, @sebmarkbage, @unstubbable)

`v19.2.3`: 19.2.3 (December 11th, 2025)

Compare Source

React Server Components

Add extra loop protection to React Server Functions (@sebmarkbage #35351)

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

Compare Source

React Server Components

Move react-server-dom-webpack/*.unbundled to private react-server-dom-unbundled (@eps1lon #35290)
Patch Promise cycles and toString on Server Functions (@sebmarkbage, @unstubbable #35289)

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

Compare Source

React Server Components

Bring React Server Component fixes to Server Actions (@sebmarkbage #35277)

`v19.2.0`

Compare Source

Below is a list of all new features, APIs, and bug fixes.

Read the React 19.2 release post for more information.

New React Features

<Activity>: A new API to hide and restore the UI and internal state of its children.
useEffectEvent is a React Hook that lets you extract non-reactive logic into an Effect Event.
cacheSignal (for RSCs) lets your know when the cache() lifetime is over.
React Performance tracks appear on the Performance panel’s timeline in your browser developer tools

New React DOM Features

Added resume APIs for partial pre-rendering with Web Streams:
- resume: to resume a prerender to a stream.
- resumeAndPrerender: to resume a prerender to HTML.
Added resume APIs for partial pre-rendering with Node Streams:
- resumeToPipeableStream: to resume a prerender to a stream.
- resumeAndPrerenderToNodeStream: to resume a prerender to HTML.
Updated prerender APIs to return a postponed state that can be passed to the resume APIs.

Notable changes

React DOM now batches suspense boundary reveals, matching the behavior of client side rendering. This change is especially noticeable when animating the reveal of Suspense boundaries e.g. with the upcoming <ViewTransition> Component. React will batch as much reveals as possible before the first paint while trying to hit popular first-contentful paint metrics.
Add Node Web Streams (prerender, renderToReadableStream) to server-side-rendering APIs for Node.js
Use underscore instead of : IDs generated by useId

All Changes

React

<Activity /> was developed over many years, starting before ClassComponent.setState (@acdlite @sebmarkbage and many others)
Stringify context as "SomeContext" instead of "SomeContext.Provider" (@kassens #33507)
Include stack of cause of React instrumentation errors with %o placeholder (@eps1lon #34198)
Fix infinite useDeferredValue loop in popstate event (@acdlite #32821)
Fix a bug when an initial value was passed to useDeferredValue (@acdlite #34376)
Fix a crash when submitting forms with Client Actions (@sebmarkbage #33055)
Hide/unhide the content of dehydrated suspense boundaries if they resuspend (@sebmarkbage #32900)
Avoid stack overflow on wide trees during Hot Reload (@sophiebits #34145)
Improve Owner and Component stacks in various places (@sebmarkbage, @eps1lon: #33629, #33724, #32735, #33723)
Add cacheSignal (@sebmarkbage #33557)

React DOM

Block on Suspensey Fonts during reveal of server-side-rendered content (@sebmarkbage #33342)
Use underscore instead of : for IDs generated by useId (@sebmarkbage, @eps1lon: #32001, #33342 #33099, #33422)
Stop warning when ARIA 1.3 attributes are used (@Abdul-Omira #34264)
Allow nonce to be used on hoistable styles (@Andarist #32461)
Warn for using a React owned node as a Container if it also has text content (@sebmarkbage #32774)
s/HTML/text for for error messages if text hydration mismatches (@rickhanlonii #32763)
Fix a bug with React.use inside React.lazy-ed Component (@hi-ogawa #33941)
Enable the progressiveChunkSize option for server-side-rendering APIs (@sebmarkbage #33027)
Fix a bug with deeply nested Suspense inside Suspense fallback when server-side-rendering (@gnoff #33467)
Avoid hanging when suspending after aborting while rendering (@gnoff #34192)
Add Node Web Streams to server-side-rendering APIs for Node.js (@sebmarkbage #33475)

React Server Components

Preload <img> and <link> using hints before they're rendered (@sebmarkbage #34604)
Log error if production elements are rendered during development (@eps1lon #34189)
Fix a bug when returning a Temporary reference (e.g. a Client Reference) from Server Functions (@sebmarkbage #34084, @denk0403 #33761)
Pass line/column to filterStackFrame (@eps1lon #33707)
Support Async Modules in Turbopack Server References (@lubieowoce #34531)
Add support for .mjs file extension in Webpack (@jennyscript #33028)
Fix a wrong missing key warning (@unstubbable #34350)
Make console log resolve in predictable order (@sebmarkbage #33665)

React Reconciler

createContainer and createHydrationContainer had their parameter order adjusted after on* handlers to account for upcoming experimental APIs

`v19.1.5`: 19.1.5 (January 26th, 2026)

Compare Source

React Server Components

Add more DoS mitigations to Server Actions, and harden Server Components (#35632 by @gnoff, @lubieowoce, @sebmarkbage, @unstubbable)

`v19.1.4`: 19.1.4 (December 11th, 2025)

Compare Source

React Server Components

Add extra loop protection to React Server Functions (@sebmarkbage #35351)

`v19.1.3`: 19.1.3 (December 11th, 2025)

Compare Source

React Server Components

Move react-server-dom-webpack/*.unbundled to private react-server-dom-unbundled (@eps1lon #35290)
Patch Promise cycles and toString on Server Functions (@sebmarkbage, @unstubbable #35289, #35345)

`v19.1.2`: 19.1.2 (December 3rd, 2025)

Compare Source

React Server Components

Bring React Server Component fixes to Server Actions (@sebmarkbage #35277)

kulshekhar/ts-jest (ts-jest)

`v29.4.6`

Compare Source

Bug Fixes

log hybrid module as warning instead of failing tests (#5144) (528d37c), closes #5130

`v29.4.5`

Compare Source

Bug Fixes

allow filtering modern module warning message with diagnostic code (c290d4d), , closes #5013

`v29.4.4`

Compare Source

Bug Fixes

revert 29.4.3 changes (25cb706), closes #5049

`v29.4.3`

Compare Source

Bug Fixes

revert 29.4.3 changes (25cb706), closes #5049

`v29.4.2`

Compare Source

`v29.4.1`

Compare Source

`v29.4.0`

Compare Source

Features

feat: support Jest 30 (84e093e)

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, 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.

vercel · 2025-08-01T07:31:10Z

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

Project	Deployment	Actions	Updated (UTC)
pgtyped	Error		Mar 21, 2026 1:39am

vercel bot deployed to Preview August 1, 2025 07:31 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 5804b78 to 20d31c9 Compare August 2, 2025 07:47

vercel bot deployed to Preview August 2, 2025 07:47 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 20d31c9 to c3d7c15 Compare August 3, 2025 13:32

vercel bot deployed to Preview August 3, 2025 13:32 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from c3d7c15 to 9dafd9b Compare August 8, 2025 17:22

vercel bot deployed to Preview August 8, 2025 17:22 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 9dafd9b to 9499e9a Compare August 9, 2025 04:48

vercel bot deployed to Preview August 9, 2025 04:48 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 9499e9a to 834d025 Compare August 10, 2025 14:10

vercel bot deployed to Preview August 10, 2025 14:10 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 834d025 to 6407581 Compare August 15, 2025 10:22

vercel bot deployed to Preview August 15, 2025 10:22 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from 6407581 to a9ab71d Compare August 16, 2025 04:54

vercel bot deployed to Preview August 16, 2025 04:55 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from a9ab71d to ce3db55 Compare August 25, 2025 11:04

vercel bot deployed to Preview August 25, 2025 11:04 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from ce3db55 to c046e1f Compare August 31, 2025 14:41

vercel bot deployed to Preview August 31, 2025 14:41 View deployment

renovate bot force-pushed the renovate/all-minor-patch branch from c046e1f to cfd668a Compare September 6, 2025 18:13

vercel bot had a problem deploying to Preview September 6, 2025 18:13 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from cfd668a to e177b2d Compare September 12, 2025 23:59

vercel bot had a problem deploying to Preview September 12, 2025 23:59 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from e177b2d to 1ba7d5e Compare September 13, 2025 23:57

vercel bot had a problem deploying to Preview September 13, 2025 23:57 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 1ba7d5e to a58cdfb Compare September 16, 2025 03:39

vercel bot had a problem deploying to Preview September 16, 2025 03:39 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from a58cdfb to 4a11444 Compare September 17, 2025 01:11

vercel bot had a problem deploying to Preview September 17, 2025 01:11 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from a3e316a to b900f36 Compare October 9, 2025 18:50

vercel bot had a problem deploying to Preview October 9, 2025 18:50 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from b900f36 to 24a29e9 Compare October 10, 2025 12:41

vercel bot had a problem deploying to Preview October 10, 2025 12:41 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 24a29e9 to 5a71645 Compare October 11, 2025 16:32

vercel bot had a problem deploying to Preview October 11, 2025 16:32 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 5a71645 to aa28b16 Compare October 17, 2025 05:49

vercel bot had a problem deploying to Preview October 17, 2025 05:50 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from aa28b16 to 061bdfe Compare October 21, 2025 01:51

vercel bot had a problem deploying to Preview October 21, 2025 01:51 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 061bdfe to 0c7061f Compare October 28, 2025 01:37

vercel bot had a problem deploying to Preview October 28, 2025 01:37 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 0c7061f to 7581013 Compare October 28, 2025 23:54

vercel bot had a problem deploying to Preview October 28, 2025 23:54 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 7581013 to b9a9c48 Compare November 3, 2025 02:54

vercel bot had a problem deploying to Preview November 3, 2025 02:54 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from b9a9c48 to fc450ab Compare November 9, 2025 04:39

vercel bot had a problem deploying to Preview November 9, 2025 04:39 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from fc450ab to cd029aa Compare November 9, 2025 21:33

vercel bot had a problem deploying to Preview November 9, 2025 21:34 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from cd029aa to d8c4c15 Compare November 12, 2025 04:03

vercel bot had a problem deploying to Preview November 12, 2025 04:03 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from d8c4c15 to b917e52 Compare December 1, 2025 19:25

vercel bot had a problem deploying to Preview December 1, 2025 19:25 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from b917e52 to b147915 Compare December 3, 2025 18:30

vercel bot had a problem deploying to Preview December 3, 2025 18:30 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from b147915 to 335bab7 Compare December 3, 2025 20:46

vercel bot had a problem deploying to Preview December 3, 2025 20:47 Failure

renovate bot force-pushed the renovate/all-minor-patch branch from 335bab7 to 1621b64 Compare December 8, 2025 23:49

fix(deps): update all non-major dependencies

e5adbbd

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

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

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

renovate bot commented Aug 1, 2025 •

edited

Loading

Uh oh!

vercel bot commented Aug 1, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

Uh oh!

Conversation

renovate bot commented Aug 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

v19.2.4: 19.2.4 (January 26th, 2026)

React Server Components

v19.2.3: 19.2.3 (December 11th, 2025)

React Server Components

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

React Server Components

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

React Server Components

New React Features

New React DOM Features

Notable changes

All Changes

React

React DOM

React Server Components

React Reconciler

v19.1.5: 19.1.5 (January 26th, 2026)

React Server Components

v19.1.4: 19.1.4 (December 11th, 2025)

React Server Components

v19.1.3: 19.1.3 (December 11th, 2025)

React Server Components

v19.1.2: 19.1.2 (December 3rd, 2025)

React Server Components

Bug Fixes

Bug Fixes

Bug Fixes

Bug Fixes

Features

Configuration

Uh oh!

vercel bot commented Aug 1, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

0 participants

renovate bot commented Aug 1, 2025 •

edited

Loading

`v19.2.4`: 19.2.4 (January 26th, 2026)

`v19.2.3`: 19.2.3 (December 11th, 2025)

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

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

`v19.1.5`: 19.1.5 (January 26th, 2026)

`v19.1.4`: 19.1.4 (December 11th, 2025)

`v19.1.3`: 19.1.3 (December 11th, 2025)

`v19.1.2`: 19.1.2 (December 3rd, 2025)

vercel bot commented Aug 1, 2025 •

edited

Loading