Repository navigation
chore(deps): update github actions - #96
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
renovate
Bot
force-pushed
the
renovate/github-actions
branch
13 times, most recently
from
October 17, 2026 20:56
a24e9f7 to
ad5b0de
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
16 times, most recently
from
October 26, 2026 18:08
dade8d5 to
add9131
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
6 times, most recently
from
November 4, 2026 19:30
a81a5dd to
05d536d
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
7 times, most recently
from
November 11, 2026 22:49
d024aea to
2025b77
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
5 times, most recently
from
November 15, 2026 04:54
547412a to
8634957
Compare
renovate
Bot
force-pushed
the
renovate/github-actions
branch
from
November 15, 2026 10:45
8634957 to
d0df9c2
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:
v2.9.2→v2.9.3v8.0.1→v8.0.2v7.0.0→v7.1.0v7.0.1→v7.0.2v5.0.1→v5.1.0652d699→1ce2d08v4.6.0→v4.8.089b1218→390088212.14.0→12.21.0v6.1.0→v6.1.177f5851→b6972e13811787→7958cfbv3.0.3→v3.0.4v2.87.25→v2.90.5Release Notes
Swatinem/rust-cache
v2.9.3Compare Source
What's Changed
New Contributors
Full Changelog: Swatinem/rust-cache@v2.9.2...v2.9.3
actions/download-artifact
v8.0.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/download-artifact@v8.0.1...v8.0.2
actions/setup-node
v7.1.0Compare Source
What's Changed
Enhancements:
Bug fixes:
Documentation updates:
Dependency updates:
New Contributors
Full Changelog: actions/setup-node@v7.0.0...v7.1.0
actions/upload-artifact
v7.0.2Compare Source
What's Changed
New Contributors
Full Changelog: actions/upload-artifact@v7.0.1...v7.0.2
azure/setup-helm
v5.1.0Compare Source
Added
Fixed
Security
Changed
docker/login-action
v4.8.0Compare Source
Full Changelog: docker/login-action@v4.7.0...v4.8.0
v4.7.0Compare Source
registry-authby @crazy-max in #1089Full Changelog: docker/login-action@v4.6.0...v4.7.0
pnpm/pnpm (pnpm)
v12.21.0: pnpm 12.21Compare Source
pnpm 12.21.0 lets
pnpm store addprepare tarball and git dependencies for offline installs. It also makes repeated installs keep their peer dependency choices and fixes severallockfile.format: v13,nodeLinker: hoisted, andpnpm deployfailures. If a pnpr server refuses a setting, pnpm now resolves locally.Minor Changes
pnpm store addrun in a project now prepares downloaded tarballs for every lockfile entry that pins them. Besides registry packages,pnpm install --offline --frozen-lockfilecan then install dependencies on a tarball URL and dependencies on a git host such as GitHub whose lockfile entry records anintegrity.Patch Changes
Installs that failed
pnpm now reads a lockfile with a mapping key longer than 1,024 characters written as
'key':, without the?marker. Before,pnpm installand other commands failed on such a lockfile withERR_PNPM_BROKEN_LOCKFILE.With
lockfile.format: v13,pnpm installno longer fails to create or rewrite the lockfile when a package declares many of its dependencies as peers.Fixed
pnpm deployfailing withlockfile.format: v13when injected workspace packages have hashed peer bindings.Frozen installs with v13 lockfiles now accept valid peer dependencies of injected workspace packages that use catalogs.
Fixed injected workspace packages that depend on themselves linking to a nonexistent directory.
pnpm installwithfrozenStoreenabled no longer fails withERR_PNPM_FROZEN_STORE_NEEDS_BUILDwhennodeLinkerishoisted.pnpm fetchwithnodeLinker: hoistedno longer populates global virtual store links or modifies linked agent skills, and it preserves an existing hoistednode_modulesdirectory #18037.A
requirements.txtbeside apyproject.tomlthat declares[tool.uv.workspace]without a[project]table no longer makes that directory a Python project.pnpm installstopped there with an error when the directory had a.venvthat pnpm did not create #18023.Peer dependencies
Repeated installs no longer change the peer dependency providers that the previous install chose. This covers adding, updating, or removing a dependency, projects that use different ranges of one dependency, dependency cycles, and injected dependencies with
autoInstallPeers: falsepnpm/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.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.
A removed dependency no longer comes back as a peer provider. Before, a direct dependency removed with
autoInstallPeers: falsecould be restored from an old peer resolution, and a removed one could still supply its old peer context.With
nodeLinker: hoistedandautoInstallPeers: false,pnpm installno longer creates duplicate copies of a package whose resolved peers are identical. A package also no longer loads a copy of its dependency that was resolved with different peer versions #18003.pnpm deploynow binds optional peers declared only inpeerDependenciesMetafor linked workspace packages. The deployed manifest and lockfile also retain these peers when filtering dependency groups.Running scripts
Scripts now stop when pnpm's process group is killed while they are starting.
Bin shims in the global virtual store no longer include the hoisted modules directory of the project that installed them #18035.
pnpm pipelinenow rebuilds local packages and reruns build scripts after it restores a shared Cargo build cache with Cargo 1.100 or newer. Before, a worktree could reuse build-script output from the worktree that created the cache.pnpr
If the pnpr server refuses a setting the install uses, or cannot return the lockfile format pnpm reads,
pnpm installandpnpm updateprint a warning and resolve locally. Cargo and Python resolution also fall back to resolving locally. pnpm now rejects a pnpr resolution of npm dependencies that does not name its lockfile format.pnpm installwithpnprServernow limits the size of the server's resolve and lockfile verification responses. An oversized response ends the request with an error.pnpm now displays pnpr error codes and reasons when remote requests fail.
Other commands and settings
pnpm setupand the install script now support PowerShell as the login shell on Linux and macOS. They addPNPM_HOMEtoPATHinprofile.ps1under$XDG_CONFIG_HOME/powershellor~/.config/powershell#18026.A
lockfileDirsetting that points at the default lockfile directory now installs the same way as leaving it unset pnpm/tasks#275.Platinum Sponsors
Gold Sponsors
v12.20.0: pnpm 12.20Compare Source
pnpm 12.20.0 records the specifiers of local directory dependencies in the experimental v13 lockfile and fixes several
nodeLinker: hoisted, peer dependency, andoverridesbugs. The bundlednode-gypno longer ships the undici version that security scanners flag. Remote resolution and shared build caches no longer work with pnpr 0.1.0-alpha.19 or older.Minor Changes
lockfile.format: v13,pnpm installrecords the dependency specifiers of local directory packages. Frozen installs reject changed specifiers even when the locked versions still satisfy them.Patch Changes
Upgrading and security
Remote resolution, shared build caches, and release notes 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.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.Resolving dependencies
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.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.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 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.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.Hoisted node linker
nodeLinker: hoisted, a package now keeps its nested copy of a dependency that it resolved at a version other than the top-level one, including a peer dependency its parent supplies. Before, pnpm could remove that copy as a duplicate or give the top-level slot to a peer variant found deeper in the graph. The package then loaded the top-level version.Lockfile and peer dependency graphs
Fixed
pnpm installkeeping stale peer bindings after dependency changes. Required dependencies no longer remain marked optional when another workspace project removes a shared package pnpm/tasks#221.Repeated installs now keep the same dependency links when packages form cycles with several peer dependency variants pnpm/tasks#221.
Fixed writing
lockfile.format: v13for dependency cycles with missing, optional, or transitive peers. Frozen installs also accept unchanged injected packages whose peers use catalogs. With--no-optional, frozen installs reject required catalog children recorded only as optional dependencies pnpm/tasks#221.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.Running scripts and runtimes
Scripts that pnpm runs in a process group of their own are now ended when pnpm is killed right after starting them. A parallel run that was killed before pnpm registered its scripts left all of them running.
When a command name matches no script and pnpm falls back to running it as a command, the install that runs before scripts now runs once. Its errors and warnings print once #17977.
Failed downloads by project-aware global runtime commands now explain which configuration applies. Node.js failures also list the global mirror settings and environment variables to check.
Other commands and settings
Fixed
pnpmoccasionally crashing on the first HTTPS request, mostly on Windows virtual machines under load. pnpm now seeds TLS randomness from the operating system's random number generator pnpm/tasks#239.Fixed
pnpm deprecate,pnpm undeprecate, andpnpm unpublishfailing with revision conflicts when a registry cache serves stale package metadata.pnpm sbomnow reports malformed workspace manifests. Before, it omitted their packages pnpm/tasks#59.Fixed
pnpm store statusreporting approved builds of git dependencies as modified when the store contains legacy build metadata.pnpm now recognizes Capawesome Cloud and RWX as CI environments.
Platinum Sponsors
Gold Sponsors
v12.19.0: pnpm 12.19Compare Source
pnpm 12.19.0 adds
pnpm fund, lets theloadednode linker handle packages that need a build, and adds theprojectScopedOptionalPeerssetting and an experimental JSON lockfile format. It also includes a security fix: an offline install error no longer prints registry credentials. pnpm now checks theenginesand platform fields of every workspace project, and many hoisted-linker and frozen-lockfile bugs are fixed.Minor Changes
Added
pnpm fund, which lists the funding URLs declared by the installed dependencies in the same treenpm fundprints. Use--jsonfor thenpm fund --jsonreport and--recursiveor--filterto report on workspace projects.pnpm fund <pkg>opens the funding URL of an installed package, and--whichpicks one when it lists several #7354.With
nodeLinker.type: loaded, packages that need a build no longer have to be listed innodeLinker.excluded. A package with a matching side-effects cache entry loads from the store. If side-effects cache reads and writes are enabled, pnpm builds an approved package once, saves the result to the side-effects cache, and then loads it from the store. This includes a build that changes no files in its package, so its script does not run again in other projects that use the same store. List a package insideEffectsCache.excludeif its build must run in every project, such as a git hook installer. pnpm materializes other cache misses, packages with native.nodeaddons, and their dependencies automatically.pnpm also scans JavaScript sources for filesystem imports and for
__dirnameorimport.meta, and materializes matching packages. The scan does not detect computed imports. List such packages innodeLinker.excluded.Added the
projectScopedOptionalPeerssetting. When it istrue, a project gets a missing optional peer dependency only if the project's own dependencies install a version of it. Another workspace project's dependencies, such as itsdevDependencies, no longer supply one.dedupePeerDependentskeeps deduplicating everything else #16666.Added the experimental
lockfile.format: v13setting. With it, pnpm writespnpm-lock.yamlin a JSON-like syntax, indented with tabs, with a trailing comma after every entry. The file is still valid YAML. The file has onepackagesentry per package version in place of thepackagesandsnapshotssections, and each entry records the versions of its peer dependencies as its properties. Updating a peer dependConfiguration
📅 Schedule: (in timezone Asia/Shanghai)
🚦 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.