Repository navigation
chore(deps): update all non-major dependencies - #115
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
4 times, most recently
from
November 14, 2026 02:39
9605230 to
d4e43eb
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 16, 2026 14:10
d4e43eb to
d74061e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
This PR body was truncated due to platform limits.
This PR contains the following updates:
^5.0.5→^5.1.0^1.64.1→^1.65.111.28.10→11.28.12^8.3.5→^8.3.8^5.0.5→^5.1.0Release Notes
vitest-dev/vitest (@vitest/browser-playwright)
v5.1.0Compare Source
🚀 Features
--last-failedto run only failed tests - by @sheremet-va in #11558 (82f63)Temporal.InstantandTemporal.ZonedDateTimeinvi.setSystemTime()- by @Prajwal2246, Prajwal2246, Claude Opus 5.5 (1M context), @hi-ogawa and Codex (GPT-6) in #11321 (f150f)--since-last-runflag - by @sheremet-va in #11516 (08bd9)node:timersandnode:timers/promise- by @hi-ogawa, OpenCode and Codex (GPT-6) in #10899 (fbe97)pointerAPI - by @macarie in #10780 (5dc09)ignoreNodeoption - by @erickserra and @AriPerkkio in #11688 (e02db)🐞 Bug Fixes
--changedfiltering - by @sheremet-va in #11621 (3a39c)watchfrom the root config in projects - by @nstepien and Claude Opus 5.5 (1M context) in #11724 (77c12)page.viewport()- by @sheremet-va in #11738 (49ff4)autoAttachSubprocessto use.tmpdirectory - by @AriPerkkio in #11632 (de5af)🏎 Performance
magic-string+rolldownfor instrumentation - by @AriPerkkio in #11648 (2470b)Promise.all- by @AriPerkkio in #11713 (f1092)View changes on GitHub
microsoft/playwright (playwright)
v1.65.1Compare Source
Bug Fixes
Browser Versions
v1.65.0Compare Source
🥟 Run tests with Bun
The test runner now runs under Bun. Bun transpiles your TypeScript test files itself, so Playwright does not use Babel or its compilation cache. Pass the
--bunflag, because without itbunx playwright testruns on Node.js:bunx --bun playwright testOur CI runs the test runner tests under Bun 1.4.3 on Linux. Some features work differently under Bun:
--only-changeddoes not follow imports.--tsconfigand the JSX options intsconfig.jsonhave no effect, and custom ESM loaders are not supported.clickinstead oflocator.click. This changes some step locations, step titles and error messages.🚨 Reports with only failures
New
failuresreporter prints failures and successful retries as they occur, followed by a summary, without progress output.New
onlyFailuresoption of the HTML, JSON and JUnit reporters keeps only tests with unexpected outcomes, flaky tests and interrupted tests:🎯 Test runner
New built-in
-exclusive-test lock runs a test only when no other tests are running. All other tests continue to run in parallel with each other:test.skip(), test.fixme(), test.fail() and test.slow() now accept only a description. It is recorded in the test annotation:
New
PLAYWRIGHT_TRANSFORM_CACHE_DIRenvironment variable sets the directory for transpiled test files, for example on a Linux machine shared with other users.New APIs
timeoutandsignalin cdpSession.send().Notable Changes⚠️
TypeScript class fields now follow
useDefineForClassFieldsfrom yourtsconfig.json, the same astsc. It is enabled forES2022and later targets, and whentargetis not specified. A field initializer that reads a constructor parameter property now fails, because the initializer runs first:Move the initialization to the constructor, or set
"useDefineForClassFields": falsein yourtsconfig.json.Actions such as locator.click(), locator.check(), locator.tap(), locator.fill(), locator.clear() and locator.selectOption() now wait for the element to be not inert. An action on an element with the
inertattribute, or inside such an element, now times out if the element stays inert.A sharded run now fails with "No tests found" when no tests match across all shards. Pass
--pass-with-no-teststo allow this. An empty shard still passes when other shards have tests.Cookie matching now follows RFC 6265. With a URL, browserContext.cookies() and apiRequestContext.cookies() no longer return host-only cookies for subdomains or
Path=/apicookies for/apiv2, and aPath=/foo/cookie does not match/foo. APIRequestContext sends a cookie without a name asCookie: xinstead ofCookie: =x, and storesSet-Cookie: tokenas a cookie without a name.Proxy credentials are no longer sent to websites. The credentials in the
proxyoption now answer only proxy challenges. To authenticate on a website, usehttpCredentials.Text that the browser does not render, such as text that is not assigned to a slot or text directly inside a closed
<details>, is no longer part of accessible names and aria snapshots. This can change the results of page.getByRole() with a name, locator.ariaSnapshot() and expect(locator).toMatchAriaSnapshot().String and
URLSearchParamsvalues of theparamsoption in APIRequestContext requests are now appended to the query that the URL already has, instead of replacing it..css,.lessand.scssimports in test files now load as empty modules instead of being removed, so the imported file must exist.The blob reporter again deletes the content of its output directory before it writes the report. Playwright 1.64 kept reports with other names.
Test locations of imported calls such as
test(in CommonJS output now point to the start of the callee, for examplea.spec.ts:3:7instead ofa.spec.ts:3:11. This is the same as in ESM.Announcements
Browser Versions
This version was also tested against the following stable channels:
pnpm/pnpm (pnpm)
v11.28.12: pnpm 11.28.12Compare Source
pnpm 11.28.12 fixes many peer dependency,
pnpm deploy, frozen-lockfile, andnodeLinker: hoistedbugs. It also includes a security fix. A${VAR}placeholder in a repository's registry URL now fails the command, so pnpm no longer sends those requests to another registry. The bundlednode-gypno longer ships the undici version that security scanners flag, and remote resolution needs pnpr 0.1.0-alpha.20 or newer.Patch Changes
Upgrading and security
A
${VAR}placeholder in a registry URL inpnpm-workspace.yamlor the project.npmrcnow fails the command. pnpm does not expand environment variables in these files. Before, pnpm ignored such a URL and resolved packages from another registry, such as npmjs.org. pnpm now warns when it ignores a placeholder in a proxy,pnprServer, oruserAgentsetting inpnpm-workspace.yaml#17762.The
node-gypbundled with pnpm no longer ships undici 6, which security scanners flag for CVE-2026-84947. On Node.js 26,node-gypdownloads through a proxy or with a custom CA file no longer crash with "invalid onError method" #17941.Remote resolution and shared build caches no longer work with pnpr 0.1.0-alpha.19 or older. pnpm now reads the capabilities a pnpr server advertises under
pnpr.protocols. Installs fail when the server does not confirm the requested resolution and verification policies. Upgrade the pnpr server before upgrading pnpm.Installs that failed
pnpm install --frozen-lockfilenow succeeds when a workspace project recorded inpnpm-lock.yamlhas an empty directory, such as a git submodule that was not checked out #17712.pnpm install --frozen-lockfilenow accepts a lockfile when an injected workspace package declares afile:orlink:dependency with backslashes, such asfile:..\vendor, or with a slash after the protocol, such asfile:/./vendor. Before, the install reported the lockfile as out of date right afterpnpm installhad written it #17720.pnpm install --frozen-lockfileandverifyDepsBeforeRunnow accept aworkspace:dependency on a project whose version is not valid semver, such asworkspace:1on a project at version1. Before, they reported the lockfile thatpnpm installhad just written as out of date.pnpm fetchno longer fails withENOENTwhennodeLinkerishoistedand the project configurespatchedDependenciesorallowBuilds.pnpm fetchalso preserves an existing hoistednode_modulesdirectory #18037.Git dependencies now accept npm's
::separator between fragment parameters, such asgithub:owner/repo#v1.0.0::path:packages/foo. Before, pnpm read the whole fragment as a branch name and failed to resolve it #17827.pnpm no longer fails to remove a dependency whose
package.jsonis malformed. It removes the dependency and keeps its bins pnpm/tasks#295.Fixed
pnpm deprecate,pnpm undeprecate, andpnpm unpublishfailing with revision conflicts when a registry cache serves stale package metadata.When a package injected through a path, such as
file:../libor../lib, gives one of its dependencies acatalog:specifier,pnpm installnow fails the way a fresh resolution does, andpnpm install --frozen-lockfilereports the lockfile as outdated. Before, both could accept the existing lockfile #17722.Peer dependencies
Repeated installs no longer change the peer dependency providers that the previous install chose. This covers adding a dependency, removing a shared package from one workspace project, and projects that use different ranges of one dependency pnpm/tasks#221.
An unchanged install keeps a valid locked peer provider even when a direct dependency provides another compatible version. Explicit
pnpm addandpnpm updaterequests take precedence over it. Required dependencies no longer remain marked optional when another workspace project removes a shared package.Workspace projects that select different versions of a peer provider no longer share one copy of the package that depends on it. This affected peers reached through an aliased dependency or a peer dependency cycle.
New workspace projects now prefer peer versions already pinned in the lockfile. Dependencies that are also optional peers no longer cause an unrelated project to select an older peer version.
With
dedupePeerDependents: false, a missing optional peer is no longer resolved from a version that only another workspace project depends on. The workspace root's dependencies still count ifresolvePeersFromWorkspaceRootistrue. Before, a tool in one project'sdevDependencies, such aswebpack-cli, could become an optional peer of another project's production dependencies #16666.pnpm installno longer gives a project an optional peer dependency that it skipped because a required peer would conflict with the project's dependencies. Before,dedupePeerDependentsmerged the project's copy of the package that declares the peer with another project's copy that resolves it #17781.pnpm installno longer fills in a missing optional peer dependency if a required peer it brings in conflicts with a version the project depends on. Before, such a peer was installed along with it and reported as unmet #17718.With
autoInstallPeersFromHighestMatch, conflicting non-semver peer dependencies now remain missing, and identical non-semver peer specifiers are preserved. Preferred registry versions no longer replace local paths or protocol-prefixed specifiers when pnpm installs missing peers pnpm/tasks#272.Fixed installation and peer dependency reporting for packages named
constructorortoString. Optional peers with these names are also recognized when declared only inpeerDependenciesMeta.Resolving and linking dependencies
A root
overridesentry that points a package at aworkspace:path, such asworkspace:./packages/foo, now also applies when a registry package depends on that package pnpm/tasks#270.Version-selector
overridesentries such as"ms@^2.0.0": "2.1.1"now apply to dependencies declared with thecatalog:protocol when the catalog entry's range matches the selector #17922.An optional dependency that declares no
os,cpu, orlibcfield is no longer skipped because its name contains only an operating system word, such asget-windowson macOS. pnpm now infers its platform from the name only when the name also has a cpu or libc token, such as-win32-x64#17774.pnpm dedupenow keeps a locked runtime version, fromdevEngines.runtimeor from a dependency'sengines.runtime, when the declared range still admits it.pnpm dedupe --checkno longer fails each time a newer Node.js release in the range comes out #17984.Resolving against a registry that sends
Cache-Control: no-cache, such as Azure Artifacts, is fast again when the lockfile already decides the version. pnpm reads the cached metadata for a pinned version, or for a range the lockfile version is proven to win, without a registry request #17758.Dependencies declared as
workspace:entries in catalogs now remain in the lockfile whenexcludeLinksFromLockfileis enabled. Frozen installs can restore these links afternode_modulesis removed pnpm/tasks#260.pnpm install --filterin a sparse checkout now counts the dependencies of workspace projects that are missing from disk when it resolves peer dependencies and marks packages as optional. The lockfile it writes no longer differs from a full checkout in those entries #17791.With
nodeLinker: hoisted,pnpm install --filterin a sparse checkout now drops previously installed workspace projects that are missing from disk from the hoistednode_modulestree. It no longer recreatesnode_modulesinside a missing project's directory. Packages that only the missing project used are also removed from the rootnode_modules.With
nodeLinker: hoistedand a custommodulesDir, pnpm now installs a workspace project's dependencies that cannot be hoisted to the root into the project'smodulesDir. The next install that relinks the project removes the copies that earlier installs left in itsnode_modules. A later install restores the project'smodulesDirwhen it was removed. Package directories that pnpm did not install are now also moved to.ignoredin a custommodulesDir.With
dedupeDirectDeps,pnpm installnow compareslink:dependencies by the directory they point at. A project'slink:dependency is removed when the workspace root links the same directory under a different path. It is kept when the root'slink:dependency has the same text but points at another directory. This also applies withnodeLinker: hoisted.pnpm installreports each removedlink:dependency once pnpm/tasks#293.A repeat
pnpm installwithnodeLinker: pnpnow applies dependency and configuration changes. Before, it printed "Already up to date" and left the lockfile unchanged.Config dependencies use the declared registry
serverTypewhen recording and installing packages pnpm/tasks#236.pnpm deploy
pnpm deployno longer fails when the deployed project depends on a workspace package that setspublishConfig.directory. pnpm installs that package from its publish directory and runs its build scripts #17771.pnpm deploynow runs the build scripts of a workspace project that it installs as afile:dependency, without a machine-specificallowBuildskey. AnallowBuildsentry that denies the project still applies #17740.pnpm deploy --offline --trust-lockfilenow reuses dependencies pinned in the source lockfile from a populated store when registry metadata is unavailable. This works with per-project lockfiles,--legacy, and npm aliases #17888.pnpm deploypreserves an injected workspace package's resolved dependencies when they differ from the workspace project's own dependencies. This also applies to packages withpublishConfig.directorypnpm/tasks#221.pnpm deploynow binds optional peers declared only inpeerDependenciesMetafor linked workspace packages. The deployed manifest and lockfile also retain these peers when filtering dependency groups.Builds, bins, and scripts
Concurrent installs into a global virtual store no longer wait on each other. A package that needs a build is built in a private directory and moved into the store once its build has finished, so another project never links a half-built package. An install with
--ignore-scriptslinks the packages it does not build from their own store directories, andpnpm store pruneremoves the build directories of installs that were interrupted #15568.Packages that an older pnpm version added to the store now run their install scripts. Before, pnpm could skip those scripts and hardlink the package's files to the store. This includes git dependencies that an older pnpm marked in a shared store as not requiring a build pnpm/tasks#189.
Fixed
pnpm store statusreporting approved builds of git dependencies as modified when the store contains legacy build metadata.pnpm store prunenow stops if a dependency link cannot be read. This keeps installed packages from being removed after an incomplete scan.When
pnpm installadds placeholder entries toallowBuildsinpnpm-workspace.yaml, it no longer copiesallowBuildsentries from other config sources into the file.Bin shims in the global virtual store no longer include the hoisted modules directory of the project that installed them #18035.
POSIX bin shims and the
pnpm,pn,pnpx, andpnxlaunchers now run inside a Nix build on macOS with the sandbox enabled. Installing again replaces the shims already innode_modules#17750.Installing no longer replaces the POSIX bin shims that a newer pnpm wrote in
node_modules/.bin.Linking bins is faster for packages that ship large native executables as bins. pnpm now reads only the first 512 bytes of a bin file to find its shebang #17361.
pnpm runandpnpm setupno longer clear the visible terminal on Windows when a project path contains non-ASCII characters.pnpm stops scripts and their descendants when it is killed during script startup pnpm/tasks#313.
Engines and runtimes
pnpm installnow fails on a workspace project's incompatibleengines.pnpm, or on its incompatibleengines.nodewithengineStrictenabled, even when the project'sos,cpu, orlibcexcludes the current platform pnpm/tasks#281.pnpm installnow checks the project'senginesfield when the project is already up to date. A repeat install of a project outside a workspace warns about an incompatible Node.js version, or fails withengineStrictenabled #17751.A workspace project that downloads its own Node.js through
devEngines.runtimenow has itsengines.nodechecked against that Node.js. Before, pnpm checked it agaConfiguration
📅 Schedule: (UTC)
* 0-3 * * 1)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.