fix(deps): update all non-major dependencies by renovate[bot] · Pull Request #117 · wolfstar-project/staryl

renovate · 2026-09-27T00:54:05Z

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Type	Update	Pending
@types/node (source)	`^24.13.5` → `^24.19.1`	devDependencies	minor	`24.19.2`
@wolfstar/cli (source)	`^2.6.0` → `^2.6.1`	devDependencies	patch	`2.8.0` (+1)
@wolfstar/decorators (source)	`^0.1.0` → `^0.1.2`	dependencies	patch
@wolfstar/http-framework (source)	`^6.2.2` → `^6.3.0`	pnpm-workspace.overrides	minor	`6.3.1`
@wolfstar/http-framework (source)	`^6.2.2` → `^6.3.0`	dependencies	minor	`6.3.1`
@wolfstar/shared-http-pieces (source)	`2.0.9` → `2.0.11`	dependencies	patch
actions/setup-node	`v7.0.0` → `v7.1.0`	action	minor
ansi-regex	`^6.3.0` → `^6.4.0`	pnpm-workspace.overrides	minor
docker/dockerfile	`1.27` → `1.28`	syntax	minor
pnpm (source)	`12.4.2` → `12.10.1`	packageManager	minor	`12.11.2` (+2)

Release Notes

wolfstar-project/stars-components (@wolfstar/cli)

`v2.6.1`

Compare Source

Patch Changes

#302 677dc1f - Fix stars dev asking to redeploy commands that did not change. The bot is no longer started (or restarted) while a build is still writing the output, so it cannot report a part of its commands, and the commands the bot registers are compared with the deployed ones rather than with the previous report, so a command reported as removed and then added again no longer prompts. Accepting the prompt while a build runs is refused with a warning instead of registering an incomplete set of commands. Thanks @RedStar071!

wolfstar-project/stars-components (@wolfstar/decorators)

`v0.1.2`

Patch Changes

#298 4391191 - Document that the PreconditionError thrown by RequiresUserPermissions and RequiresClientPermissions is emitted as chatInputCommandDenied, contextMenuCommandDenied, or interactionHandlerDenied with @wolfstar/http-framework 6.3.0, instead of commandError. Thanks @RedStar071!

`v0.1.1`

Patch Changes

#253 05a8443 - fix(deps): update all non-major dependencies Thanks @renovate!

wolfstar-project/stars-components (@wolfstar/http-framework)

`v6.3.0`

Compare Source

Minor Changes

#300 d09da7d - Add preconditions, the checks that run before a command, its autocomplete, or an interaction handler, following @sapphire/framework. A Precondition piece in the new preconditions store implements chatInputRun, contextMenuRun, autocompleteRun and/or interactionHandlerRun and answers with ok() or error() (a PreconditionError for the piece); a piece with a position is global and runs in ascending order of it. The new preconditions option of Command.Options and InteractionHandler.Options lists the ones to run, by name, by name with a context, or as a PreconditionFunction, and an entry can be an array: the list is an AND, an array nested in it an OR, one nested in that an AND again, like ['Connect', ['Moderator', ['DJ', 'SongAuthor']]]. The list can be { entries, mode: PreconditionRunMode.Parallel } to start every entry at once. The first denial skips the method and is emitted as chatInputCommandDenied, contextMenuCommandDenied, autocompleteDenied or interactionHandlerDenied. A piece with no method for a chat input or context menu command denies it; for an autocomplete or an interaction handler it is skipped.

New events: preChatInputCommandRun, preContextMenuCommandRun, chatInputCommandAccepted, contextMenuCommandAccepted, autocompleteAccepted and interactionHandlerAccepted. commandRun, autocompleteRun and interactionHandlerRun are now emitted after the preconditions pass, so a denied interaction does not emit them; without preconditions nothing changes. AllFlowsPrecondition, PreconditionStore, runPreconditions and the related types are exported, and Identifiers gets PreconditionMissingChatInputHandler and PreconditionMissingContextMenuHandler. PreconditionRunMode, PreconditionRunCondition and the array types are exported. There are no built-in preconditions. Thanks @RedStar071!
#298 4391191 - Route the UserError a command, an autocomplete handler, or an interaction handler throws to new *Denied events instead of the *Error ones. chatInputCommandDenied and contextMenuCommandDenied (also Events.ChatInputCommandDenied and Events.ContextMenuCommandDenied) replace commandError for commands, autocompleteDenied replaces autocompleteError, and interactionHandlerDenied replaces interactionHandlerError; all of them carry (error: UserError, context). Anything that is not a UserError still goes to the *Error events, and the error event and the HTTP response are unchanged. The new isUserError helper does the check, falling back to the shape of the error for a UserError from another copy of the package.

This changes what a listener on commandError, autocompleteError, or interactionHandlerError receives: a UserError (including the PreconditionError of @wolfstar/decorators) no longer reaches it, so a listener that replies to the user with one has to move to the matching *Denied event. Thanks @RedStar071!

Patch Changes

Updated dependencies [677dc1f]:
- @wolfstar/cli@2.6.1

wolfstar-project/stars-components (@wolfstar/shared-http-pieces)

`v2.0.11`

Patch Changes

#298 4391191 - Stop reporting a UserError to Sentry from the error listener. With @wolfstar/http-framework 6.3.0 a UserError is also emitted as a *Denied event, and the commandError, autocompleteError, and interactionHandlerError listeners no longer receive it. Thanks @RedStar071!
Updated dependencies [d09da7d, 4391191]:
- @wolfstar/http-framework@6.3.0

`v2.0.10`

Patch Changes

#253 05a8443 - fix(deps): update all non-major dependencies Thanks @renovate!
Updated dependencies [05a8443, 814c8f9]:
- @wolfstar/env-utilities@2.3.1
- @wolfstar/http-framework@6.2.0

actions/setup-node (actions/setup-node)

`v7.1.0`

Compare Source

What's Changed

Enhancements:

Add support for mise.toml file by @gperdomor in #1421
Support absolute paths in node-version-file by @v-mahabaleshwars in #1633

Bug fixes:

Add Node version validation and manifest fetch retry by @v-jitenderpalsingh in #1580

Documentation updates:

README.md: bump actions/checkout to latest version 7 by @deining in #1578
docs: add V7 ESM migration and NODE_AUTH_TOKEN behavior change by @v-gowridurgad in #1593
Fixed cache recommendation syntax by @SubJunk in #1603

Dependency updates:

Update workflow pins and migrate Node matrices to modern versions by @v-HarithaVattikuti in #1583
Upgrade @actions/cache to 6.2.0 by @philip-gai in #1584
Pin @types/node to v24 by @v-priyagupta108 in #1585
Override brace-expansion to 5.0.8 by @v-priyagupta108 with @Copilot in #1599
Upgrade actions/checkout from 7.0.0 to 7.0.1 by @dependabot in #1598
Upgrade prettier from 3.8.4 to 3.9.6 by @dependabot in #1590
Upgrade @vercel/ncc from 0.44.0 to 0.45.0 by @dependabot in #1610
Upgrade pnpm/action-setup from 6.0.9 to 6.0.10 by @dependabot in #1602
Upgrade baseline-browser-mapping from 2.10.38 to 2.11.22 by @dependabot in #1629
Upgrade @types/semver from 7.7.1 to 7.8.0 by @dependabot in #1616
Upgrade @typescript-eslint/parser from 8.62.0 to 8.70.0 by @dependabot in #1615
Upgrade pnpm/action-setup from 6.0.10 to 6.1.0 by @dependabot in #1631
Upgrade jest-each from 30.4.1 to 30.5.2 by @dependabot in #1636
Upgrade eslint-plugin-n from 18.1.0 to 18.3.0 by @dependabot in #1638
Update dependencies and add license files by @v-HarithaVattikuti in #1642
Upgrade eslint from 10.5.0 to 10.11.0 and package.json from 7.0.0 to 7.1.0 by @dependabot in #1635

New Contributors

@v-jitenderpalsingh made their first contribution in #1580
@philip-gai made their first contribution in #1584
@gperdomor made their first contribution in #1421
@SubJunk made their first contribution in #1603

Full Changelog: actions/setup-node@v7.0.0...v7.1.0

chalk/ansi-regex (ansi-regex)

`v6.4.0`

Compare Source

Match OSC sequences using the C1 introducer 79e112d

pnpm/pnpm (pnpm)

`v12.10.1`: pnpm 12.10.1

Compare Source

This release fixes pnpm install failures after an overrides change and on a filtered frozen install with catalogPrune. It also fixes several bugs in the experimental nodeLinker.type: loaded, which now keeps its generated files in node_modules.

Patch Changes

With nodeLinker.type: loaded, pnpm now writes its generated files to node_modules, which projects already ignore in git. The store manifest and loader are node_modules/.pnpm/.store-manifest.json and node_modules/.pnpm/.store-loader.mjs. Bin shims are in node_modules/.bin.

Earlier versions wrote .pnpm-store.json and .pnpm-store-loader.mjs to the project root, and a .pnpm directory to the root and to each workspace package. Delete them after reinstalling.
With nodeLinker.type: loaded, packages that ship their own node_modules directory, such as npm with its bundled dependencies, now load from the store. Before, one such package in the install stopped every Node.js process from starting.
With nodeLinker.type: loaded, scripts can now run a Node.js runtime installed through devEngines.runtime. Before, every script that called node re-ran its own shim until it failed with "Argument list too long".
With nodeLinker.type: loaded, Node.js processes start faster. In a project with 13,000 stored files, the startup overhead per process dropped from 67 ms to 18 ms.
pnpm install no longer fails with ERR_PNPM_NO_MATCHING_VERSION after a change to overrides when the lockfile resolves an optional peer dependency to an npm alias of another package #16654.
A frozen install with catalogPrune no longer removes catalog entries that pnpm-lock.yaml still records. Before, pnpm install --frozen-lockfile --filter failed with ERR_PNPM_LOCKFILE_CONFIG_MISMATCH when some workspace projects were missing from disk #16638.
pnpm install --fix-lockfile no longer removes the deprecated and hasBin fields from lockfile entries #6600.
With enableGlobalVirtualStore, an install that updates node_modules now repairs a package in the global virtual store that an interrupted install left without some of its dependency links or package files. Before, such an install kept the incomplete package if the project's node_modules already recorded it #16642.
pnpm install now skips the Cargo and Python projects inside a nested directory that has its own pnpm-workspace.yaml or .git directory, such as a git worktree of the same workspace or a separate clone.
The Request took warning for package metadata now starts timing when pnpm sends the request. Before, it also counted the time the request waited for a free request slot, so large installs printed it for requests the registry answered quickly.

Platinum Sponsors

Gold Sponsors

`v12.10.0`: pnpm 12.10.0

Compare Source

This release adds an experimental loaded node linker, lets pnpm-lock.yaml record resolution settings, and reads cached registry metadata faster. It also carries several security fixes, including one that stops a dependency version from writing files outside the global virtual store.

Minor Changes

Added experimental nodeLinker: { type: loaded } installation. Compatible dependencies load directly from the content-addressable store through an automatically registered Node.js loader. nodeLinker.excluded selects packages and their dependency trees to install in the global virtual store.
lockfile.includeResolutionSettings: true makes pnpm-lock.yaml record autoDedupe, dedupeInjectedDeps, dedupePeerDependents and linkWorkspacePackages. Installs then treat a lockfile that records other values as outdated. A lockfile that records autoDedupe is reused by later installs on any machine, so pnpm run after pnpm install --frozen-lockfile no longer starts another install #16583.

Patch Changes

Security

pnpm install now prevents dependency versions with path traversal from writing files outside the global virtual store.
pnpm now verifies locked config dependencies against their registry before installing them. Config dependencies must come from an npm registry. The lockfile can no longer replace the integrity of a config dependency pinned with version+integrity.
Lockfile verification now checks the tarballs inside a variations resolution against the registry. A name@version lockfile entry with an empty variations resolution is now rejected.
pnpm audit signatures now verifies signatures against the integrity recorded in the lockfile. Packages without a recorded integrity cannot pass signature verification.
pnpm install and pnpm publish now reject archive metadata larger than 64 MiB before reading it into memory. Publishing a pre-built tarball also rejects manifests and README files larger than 64 MiB.
Two URL or local path dependencies no longer share a virtual store directory when one URL has +, #, :, or ? where the other has /. Such dependencies, including git dependencies pinned with #, now get a hash suffix on their directory name.
The warning about an ignored project .npmrc registry setting no longer prints the username and password of a URL-scoped key such as //user:password@registry.example.com/${PATH}/:_authToken.

Installing and resolving dependencies

pnpm install now fails with ERR_PNPM_UNSUPPORTED_PROTOCOL when a dependency uses a specifier with a protocol pnpm does not support, such as Yarn's patch:. On Windows, such a specifier failed with os error 123. On other platforms, pnpm linked it to a directory that does not exist. Reading a package.json that fails now names the file #16590.
pnpm install now fails with ERR_PNPM_PACKAGE_MANIFEST_INVALID_ATTRIBUTE when a project declares a dependency whose specifier is not a string, such as "is-positive": 42. Before, the dependency was silently left out of the lockfile. A readPackage hook can still correct the specifier.
Fixed pnpm install failing with ERR_PNPM_CMD_SHIM_RESOLVE_PATH when an executable's parent directory contains a dangling symlink.
pnpm install --frozen-lockfile no longer fails with ERR_PNPM_RESOLUTION_SHAPE_MISMATCH when a name@version lockfile entry has a resolution served by a custom fetcher pnpm/tasks#108.
pnpm install --fix-lockfile repairs a lockfile whose importer references a package that has no snapshot entry, as left by a badly merged lockfile. It failed with ERR_PNPM_LOCKFILE_MISSING_DEPENDENCY since 12.8.0 #16618.
When a dependency moves an exact dependency of its own to an older version, a peer dependency that pnpm installed automatically now moves with it. Before, pnpm install and pnpm dedupe kept the newer locked version of the peer, so the lockfile held two copies of it, for example two copies of vue pnpm/tasks#61.
pnpm dedupe now reads registry metadata for a dependency pinned to an exact version, as pnpm install does. If the registry metadata disagreed with the package's package.json, the lockfile it wrote depended on whether minimumReleaseAge was set #16615.

Speed and size

Dependency resolution reads cached registry metadata faster. The metadata cache moved to <cache-dir>/v12/, so the first install after upgrading downloads registry metadata again. A damaged cache entry is downloaded again, or reported as an error when --offline is set. pnpm cache prune also removes the metadata cache that older pnpm versions wrote under <cache-dir>/v11/ #13512.
Package metadata requests no longer wait behind queued tarball downloads when maxSockets or a proxy limits the connections to a registry. Large installs resolve faster and print fewer Request took warnings.
Sped up installs in large workspaces on macOS when the dependency links already exist. pnpm now keeps a link that already points at the right package without trying to create it first. Relinking the direct dependencies of 1,000 workspace projects took 45 ms, down from 116 ms pnpm/tasks#65.
Commands in a project that pins a different pnpm version start about 13 ms faster on macOS. pnpm now runs the pinned version's binary directly, without the shell script in front of it pnpm/tasks#66.
The pnpm binary is about 0.9 MB smaller, and the arm64 Linux binary is about 1 MB smaller still.

Running scripts and commands

pnpm run no longer prints [ELIFECYCLE] Command failed ... after Ctrl+C ends the script. pnpm still exits the way the script's shell did: on Windows with the shell's exit code (cmd reports -1073741510, PowerShell 1), on Unix by re-raising SIGINT #16579.
pnpm run "/<regex>/" now accepts JavaScript regular expression syntax such as lookahead and lookbehind. A selector like "/^hello:(?!b).*$/" failed with ERR_PNPM_NO_SCRIPT #16604.
pnpm run and pnpm exec now forward --config.* command-line flags to the install started by verifyDepsBeforeRun pnpm/tasks#60.
On Windows, a process started by pnpm run or pnpm exec can again start a child with CREATE_BREAKAWAY_FROM_JOB. That child keeps running after pnpm exits, even if the command fails #16628.
Empty nodeOptions values from command-line flags and environment variables now override lower-priority settings. Scripts retain NODE_OPTIONS from the parent environment or extraEnv when nodeOptions is empty.
pnpm now reads the failIfNoMatch setting from pnpm-workspace.yaml, so a filter that matches no workspace project exits with code 1 when the setting is true. The new --no-fail-if-no-match flag turns the setting off for one command #16577.

Configuration, setup, and pnpm versions

pnpm config get --global and pnpm config list --global now show only the global configuration, also when run inside a project. Settings from the project's pnpm-workspace.yaml and .npmrc were included before. The same applies to --location=global #16598.
pnpm now prints config warnings, such as an unset environment variable in .npmrc, when loading the config fails.
pnpm 11 releases older than 11.28.4 can run pnpm 12 again when the packageManager field pins it. Since 12.9.0 they failed with SyntaxError: Invalid or unexpected token #16594.
On Windows, pnpm self-update no longer runs the update a second time when it replaces a pnpm.cmd linked by pnpm 12.8 or older. cmd.exe read on in the replaced pnpm.cmd, printed an error about a command that is not recognized, and ran the new pnpm once more #16573.
pnpm setup now puts $PNPM_HOME/bin first on PATH in login shells that inherited it further down, such as the VS Code terminal on macOS. Before, another node took precedence over the one installed by pnpm runtime set node -g. Run pnpm setup again to update the block in your shell config #16635.
pnpm setup now names the shell config file even if it is already up to date #16608.

Updating, auditing, and publishing

pnpm update --latest now applies the savePrefix setting when it rewrites a dependency whose range has no operator of its own, such as <2.0.0.
The interactive pnpm audit --fix picker now shows each patched version with the saveExact and savePrefix style that the override is written with #13209.
pnpm unpublish <pkg>@<version> now deletes the tarball under the registry's path when the registry is served under one, such as Gitea's npm registry. It used to send the delete to the host root and report success without removing the version #16568. It also no longer mistakes a sibling path such as /npm-mirror/ for the registry path /npm/ pnpm/tasks#94.

Output and messages

A warning about a project's devEngines or packageManager pin is now printed to stderr. A command such as pnpm cache path or pnpm list --json keeps only its own output on stdout #16584.
pnpm list now reports the correct package paths when nodeLinker is hoisted #9593.
Resolution errors now name the failing dependency and its parent packages. Fatal errors appear as structured error records with their error codes when using --reporter=ndjson.
The error for an invalid git repository in the lockfile now has the code ERR_PNPM_INVALID_GIT_REPOSITORY. Its message now lists every rejected form of the value.
pnpm runtime --help and pnpm help runtime now name the set subcommand and the runtimes it accepts #16580.

Platinum Sponsors

Gold Sponsors

`v12.9.1`: pnpm 12.9.1

Compare Source

This release moves the WebContainer build into a separate @pnpm/wasm package, shrinks the pnpm package back to about 4 MB, and fixes pnpm publish with provenance from GitLab CI.

Patch Changes

The WebAssembly build for StackBlitz WebContainers now ships as a separate @pnpm/wasm package. The pnpm and @pnpm/exe packages no longer include it, which brings their unpacked size back from about 55 MB to about 4 MB. In a WebContainer, install @pnpm/wasm with npm to get the pnpm command.
pnpm publish with provenance from GitLab CI is no longer rejected by the npm registry with a 422 error. The provenance statement now includes the GitLab CI variables in invocation.parameters, as npm does #16551.
pnpm audit signatures now uses the TLS settings of the redirect target when a registry redirects its signing-keys request, for example to registry.npmjs.org. A cafile scoped to a private registry no longer makes the redirected request fail #16541.
Fixed pnpm install --frozen-lockfile rejecting an up-to-date lockfile when an injected workspace package uses a catalog entry in peerDependencies #16557.
The [<since>] filter selector works again with Git 2.24 through 2.27 #16561. With Git older than 2.24, the selector now fails with an error that names the required Git version.

It also detects changes in projects whose directory names contain non-ASCII characters. Such a change used to be credited to the parent project. changedFilesIgnorePattern and testPattern now match changed files whose names contain non-ASCII characters.
The pnpm executable is about 10% smaller. On macOS arm64 it went from 45.1 MB to 40.3 MB.
Sped up trust downgrade checks for packages with long release histories.
With optimisticRepeatInstall: false, pnpm install now runs the projects' own lifecycle scripts, such as prepare, even when node_modules is already up to date #16545.
pnpm self-update now fails for Homebrew-installed pnpm and prints the brew upgrade command for the installed formula, such as brew upgrade pnpm or brew upgrade pnpm@11. It used to install a second copy of pnpm that the Homebrew one kept shadowing #16547.

Platinum Sponsors

Gold Sponsors

`v12.9.0`: pnpm 12.9

Compare Source

This release runs pnpm in StackBlitz WebContainers, adds a per-registry networkConcurrency setting, and records every installed project in the store. It also carries a security fix for pnpm login.

Minor Changes

pnpm now automatically uses WebAssembly in StackBlitz WebContainers, including when installation scripts are disabled. Native installations continue to use the native executable when installation scripts are enabled.
A registries entry can now set networkConcurrency, the most requests pnpm keeps in flight to that registry's origin. Requests to other registries keep the overall limit. The setting may live in pnpm-workspace.yaml or the global config.yaml.
```
registries:
  https://npm.corp.example.com/:
    scopes: ["@acme"]
    networkConcurrency: 4
```
pnpm install now records every project it installs in the store's projects directory, as a symlink to the project directory. A --frozen-store install without the global virtual store still records nothing. Only projects that used the global virtual store were recorded before #6929.

Patch Changes

pnpm login no longer forwards credentials in its request body to another origin during redirects.

Installing packages

Fixed pnpm install failing on Android with ERR_PNPM_STORE_DIR_ACQUIRE_OPERATION_LOCK #16508.
pnpm install --frozen-lockfile again succeeds when a workspace project recorded in pnpm-lock.yaml has no directory, such as a project left out of a Docker build context. It still fails if the project's directory exists without a package.json #16453.
pnpm install --frozen-lockfile no longer requires a pnpm-lock.yaml in a project that has no dependencies. It also succeeds when pnpm-lock.yaml records only the pinned pnpm version, as other commands write it when they run before the first install #16477.
Fixed pnpm install --frozen-lockfile rejecting a fresh lockfile when an injected workspace dependency has an optional peer supplied by another workspace project #16428.
With nodeLinker: hoisted, a filtered install now keeps the packages of the workspace projects an earlier install put in node_modules. This also covers the install that pnpm --filter <selector> run and pnpm --filter <selector> exec start before the command. Before, these installs removed every package that only the unselected projects needed #16483.
pnpm install with nodeLinker: hoisted now refreshes directories supplied by custom fetchers when reinstalling. pnpm also keeps the symlinks inside those directo

❗ Important

✂ PR body was truncated to here.

Configuration

📅 Schedule: (UTC)

Branch creation
- "before 12pm on Sunday"
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 was generated by Mend Renovate. View the repository job log.

coldtea-pr-lens · 2026-09-27T00:54:09Z

◈ PR Lens

Note

renovate[bot] opened this pull request, so PR Lens left it undrawn. Comment @pr-lens draw to draw it

_{github.comment.notice: false in .github/pr-lens.yml turns this note off}

socket-security · 2026-09-27T00:54:26Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Package	Supply Chain Security	Quality	Maintenance
@wolfstar/shared-http-pieces@2.0.9 ⏵ 2.0.11		⁺¹	⁺¹
@wolfstar/decorators@0.1.0 ⏵ 0.1.2	⁺¹		⁺⁷
@wolfstar/cli@2.6.0 ⏵ 2.6.1	⁺¹		⁺¹
@types/node@24.13.5 ⏵ 24.19.1	⁺¹	⁺¹
@wolfstar/http-framework@6.2.2 ⏵ 6.3.0	⁺¹	⁺¹	⁺¹

View full report

renovate · 2026-10-11T22:04:33Z

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

renovate Bot added the dependencies Pull requests that update a dependency file label Sep 27, 2026

renovate Bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 66d1de5 to bd66f1f Compare October 5, 2026 00:38

renovate Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from eb47ea6 to d33d1e8 Compare October 8, 2026 10:45

renovate Bot changed the title ~~fix(deps): update all non-major dependencies~~ chore(deps): update all non-major dependencies Oct 8, 2026

renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 9490ed1 to 3c0ddbd Compare October 10, 2026 12:55

renovate Bot changed the title ~~chore(deps): update all non-major dependencies~~ fix(deps): update all non-major dependencies Oct 10, 2026

renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 6f7b535 to 3f071cb Compare October 11, 2026 05:13

fix(deps): update all non-major dependencies

e9d2e0c

renovate Bot force-pushed the renovate/all-minor-patch branch from 3f071cb to e9d2e0c Compare October 11, 2026 12:38

[autofix.ci] apply automated fixes

f1f3bf8

RedStar071 approved these changes Oct 14, 2026

View reviewed changes

kodiakhq Bot merged commit 84080fe into main Oct 14, 2026
8 checks passed

kodiakhq Bot deleted the renovate/all-minor-patch branch October 14, 2026 19:49

Navigation Menu

Repository navigation

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

fix(deps): update all non-major dependencies#117
kodiakhq[bot] merged 2 commits into
mainfrom
renovate/all-minor-patch

renovate Bot commented Sep 27, 2026 •

edited

Loading

Uh oh!

coldtea-pr-lens Bot commented Sep 27, 2026

Uh oh!

socket-security Bot commented Sep 27, 2026 •

edited

Loading

Uh oh!

renovate Bot commented Oct 11, 2026

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Conversation

renovate Bot commented Sep 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

What's Changed

Enhancements:

Bug fixes:

Documentation updates:

Dependency updates:

New Contributors

v12.10.1: pnpm 12.10.1

Patch Changes

Platinum Sponsors

Gold Sponsors

v12.10.0: pnpm 12.10.0

Minor Changes

Patch Changes

Security

Installing and resolving dependencies

Speed and size

Running scripts and commands

Configuration, setup, and pnpm versions

Updating, auditing, and publishing

Output and messages

Platinum Sponsors

Gold Sponsors

v12.9.1: pnpm 12.9.1

Patch Changes

Platinum Sponsors

Gold Sponsors

v12.9.0: pnpm 12.9

Minor Changes

Patch Changes

Installing packages

Configuration

Uh oh!

coldtea-pr-lens Bot commented Sep 27, 2026

◈ PR Lens

Uh oh!

socket-security Bot commented Sep 27, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

renovate Bot commented Oct 11, 2026

Edited/Blocked Notification

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate Bot commented Sep 27, 2026 •

edited

Loading

`v12.10.1`: pnpm 12.10.1

`v12.10.0`: pnpm 12.10.0

`v12.9.1`: pnpm 12.9.1

`v12.9.0`: pnpm 12.9

socket-security Bot commented Sep 27, 2026 •

edited

Loading