Skip to content

chore(deps): update mise tools - #1462

Merged
pirosiki197 merged 1 commit into
mainfrom
renovate/mise-tools
Nov 1, 2026
Merged

pirosiki197 merged 1 commit into
mainfrom
renovate/mise-tools

Conversation

@trap-renovate

@trap-renovate trap-renovate Bot commented Oct 31, 2026

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Confidence
buf tools minor 1.73.0 → 1.75.0 age confidence
go:github.com/sqldef/sqldef/v3/cmd/mysqldef tools patch 3.11.26 → 3.11.29 age confidence
golangci-lint tools minor 2.14.0 → 2.15.0 age confidence
helm tools patch 4.3.0 → 4.3.1 age confidence
kubectl tools patch 1.37.1 → 1.37.2 age confidence
kustomize tools patch 5.8.1 → 5.8.3 age confidence
pnpm (source) tools minor 11.27.0 → 11.28.10 age confidence

Release Notes

bufbuild/buf (buf)

v1.75.0

Compare Source

  • Fix buf build dropping message_set_wire_format, weak field options, and MessageSet
    extensions, and truncating MessageSet extension ranges, when a file has an unused import.
  • Fix LSP crash when hovering on a CEL string literal containing a byte that is not valid UTF-8,
    such as '\x95' in a protovalidate rule.
  • Add BUF_DEBUG, BUF_LOG_FORMAT, and BUF_TIMEOUT environment variables as defaults for the
    --debug, --log-format, and --timeout global flags. Flags take precedence when set.
  • Add support to images for option dependencies declared with the import option syntax in
    edition 2024 and later.
  • Add support for Protobuf edition 2026.
  • Update built-in Well-Known Types to Protobuf v36.2.
  • Update managed mode to skip cc_enable_arenas for edition 2026 files, where the option was
    removed.
  • Fix buf convert and buf curl ignoring the (pb.enumvalue.json).string option for enum
    value JSON names.

v1.74.0

Compare Source

  • Improve the performance of the PROTOVALIDATE lint rule, which is now up to 3x faster
    and allocates less memory on modules using cel rules or example values.
  • Send the module name of each file to check plugins, which is available as
    FileDescriptor.ModuleName() in bufplugin-go v0.11.0 and later.
  • Update buf curl to automatically use HTTP/2 prior knowledge for http URLs when server
    reflection, the gRPC protocol, or a bidirectional streaming method is used, since all of these
    require HTTP/2. The --http2-prior-knowledge flag is no longer required in these cases.
  • Add --stdin-filepath flag to buf format, which reads a single .proto file from
    stdin and writes the formatted result to stdout. The path is not read from disk, and is
    only used to report parse errors and diffs.
  • Fix buf convert panic when converting images that contain files without a syntax
    declaration or with unused imports.
  • Fix buf generate with strategy: directory and include_imports: true adding imports
    to the CodeGeneratorRequest of the directory that imports them. Imports are now split
    by directory into their own requests, the same as non-imports.
  • Fix configuration files silently accepting unquoted values that start with !, such as
    ignore: [!foo/bar.proto]. Previously they parsed as empty strings, now they rejected
    with an error.
  • Fix lint comment ignores on proto2 group fields being ignored.
  • Update the LSP to support named generation templates such as buf.go.gen.yaml and
    buf.gen.go.yaml.
  • Improve the buf curl error message for methods that accept a single request message.
  • Add --config flag to buf lsp serve to use a buf.yaml file or data in place of
    discovering buf.yaml files. Workspaces are resolved from the editor's root folder.
  • Deduplicate remote input fetches within a single command invocation, so that multiple
    inputs in a buf.gen.yaml that resolve to the same archive, git repository, or image
    are fetched once instead of once per input.
  • Fix intermittent concurrent map write crash when compiling Editions files.
  • Fix Edition 2024 handling of enum value features, STRICT default symbol visibility, and
    source locations of export/local types.
sqldef/sqldef (go:github.com/sqldef/sqldef/v3/cmd/mysqldef)

v3.11.29

Compare Source

v3.11.28

Compare Source

v3.11.27

Compare Source

golangci/golangci-lint (golangci-lint)

v2.15.0

Compare Source

Released on 2026-10-16

  1. Linters new features or changes
    • errcheck: from 1.20.0 to 1.30.0
    • exhaustive: from 0.13.0 to 0.15.0 (⚠️ changes)
    • gocognit: from 1.2.1 to 1.3.0
    • golines: from 0.15.0 to 0.16.0
    • govet-modernize: from 0.50.0 to 0.52.0
    • loggercheck: from 0.12.0 to 0.13.0
    • predeclared: from 0.2.2 to 0.3.0
    • wrapcheck: from 2.12.0 to 2.13.0
  2. Linters bug fixes
    • bidichk: from 0.3.3 to 0.3.4
    • canonicalheader: from a25c71c to e18e5c5
    • gofumpt: improve deprecation logs
    • gosec: improve concurrency default value
    • iface: from 1.5.1 to 1.5.3
    • paralleltest: from 1.0.15 to 1.0.16
    • revive: from 1.17.0 to 1.17.1
    • revive: the rules context-keys-type, errorf, modifies-value-receiver, range-val-address, string-of-int, time-equal, time-naming, unexported-return, unhandled-error, var-declaration are working (less randomly).
    • rowserrcheck: from c5f79b8 to e0740d5
    • staticcheck: from 0.8.1 to 0.8.2
  3. Bug fixes
    • fix: compute custom version hash with module versions
    • fix: env vars loading (related to revive)

⚠️ Changes of the exhaustive linter:

  • The replaced options still exists, and partially works, but they are deprecated.
  • The options explicit-exhaustive-switch and explicit-exhaustive-map have been replaced by explicit-exhaustive.
  • The check the value map has been replaced by mapliteral.
  • The option ignore-enum-members (string) has been replaced by ignore-constants (slice).
  • The option ignore-enum-types (string) has been replaced by ignore-types (slice).
  • New report messages.
  • The linter is a now a "slow" linter.
helm/helm (helm)

v4.3.1: Helm v4.3.1

Compare Source

Helm v4.3.1 is a patch release. Users are encouraged to upgrade for the best experience.

The community keeps growing, and we'd love to see you there!

  • Join the discussion in Kubernetes Slack:
    • for questions and just to hang out
    • for discussing PRs, code, and bugs
  • Hang out at the Public Developer Call: Thursday, 9:30 Pacific via Zoom
  • Test, debug, and contribute charts: ArtifactHub/packages

Notable Changes

Installation and Upgrading

Download Helm v4.3.1. The common platform binaries are here:

This release was signed with 208D D36E D5BB 3745 A167 43A4 C7C6 FBB5 B91C 1155 and can be found at @​scottrigby keybase account. Please use the attached signatures for verifying this release using gpg.

The Quickstart Guide will get you going from there. For upgrade instructions or detailed installation notes, check the install guide. You can also use a script to install on any system with bash.

What's Next

  • 4.3.2 and 3.22.2 are the next patch releases scheduled for November 11, 2026
  • 4.4.0 is the next minor release scheduled for January 13, 2027. There will be no further Helm 3 minor releases (see https://helm.sh/blog/helm-v3-end-of-life)

Changelog

  • chore(deps): bump otlploghttp and stdoutlog to v0.21.0 c0d08d0 (Terry Howe)
  • chore(deps): bump the k8s-io group across 1 directory with 7 updates 0c0146e (dependabot[bot])
  • fix: bump golang.org/x/net to v0.61.0 (#​32758) dd91731 (Terry Howe)
  • fix(linters): update golangci-lint to v2.14.0 (#​32744) 3a376b2 (Ruslan Shaydullin)
  • fix(action): wait for CRD establishment under HookOnlyStrategy (#​32672) 5fed6a5 (Pujitha Paladugu)
  • chore(deps): bump sigs.k8s.io/controller-runtime from 0.25.1 to 0.25.2 (#​32726) b227bf4 (dependabot[bot])
  • chore(deps): bump sigs.k8s.io/kustomize/kyaml from 0.21.1 to 0.21.2 (#​32715) af79b8e (dependabot[bot])
  • chore(deps): bump go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc ab6b245 (dependabot[bot])
  • chore(deps): bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp (#​32665) 0f20617 (dependabot[bot])
  • chore(deps): bump go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc (#​32664) e26e158 (dependabot[bot])
  • chore(deps): bump go.opentelemetry.io/otel/exporters/otlp/otlptrace (#​32663) 23ab1c5 (dependabot[bot])
  • chore(deps): bump go.opentelemetry.io/otel/sdk from 1.44.0 to 1.45.0 (#​32662) 8303180 (dependabot[bot])
kubernetes/kubernetes (kubectl)

v1.37.2

Compare Source

See kubernetes-announce@. Additional binary downloads are linked in the CHANGELOG.

See the CHANGELOG for more details.

kubernetes-sigs/kustomize (kustomize)

v5.8.3

Compare Source

This release eliminates dependencies and compressed blobs that were an issue when bumping kustomize-in-kubectl.
No functional changes in kustomize.

chore

#​6310: chore: bump to Go 1.27 and latest kube-openapi
#​6318: Update kyaml to v0.21.3
#​6320: Update cmd/config to v0.21.3
#​6321: Update api to v0.21.3

v5.8.2

Compare Source

Introduction

In this release, we implemented refactoring to update dependencies and add new features.

This release adds the kustomize edit add configuration and kustomize edit remove component commands. #​6037 #​6083
The built-in OpenAPI schema is now loaded from a pre-compiled bundle embedded in the binary. #​6190
The schema itself is still based on Kubernetes v1.21.2, so the output of kustomize build is not expected to change. If you notice any difference, please file an issue.

Feature

#​6037: feat: add support for 'kustomize edit add configuration' command
#​6083: Add kustomize edit remove component command

fix

#​6263: fix: report an error when the fetched openapi schema is not JSON

Dependencies

#​6075: update go 1.25.7
#​6078: bump go-git and x/crypt
#​6085: update otel lib to v1.40.0
#​6134: drop 'go-spew' dependencies and update dependencies
#​6138: bump k8s.io/kube-openapi, drop github.com/mailru/easyjson
#​6186: bump/go v1.26.5
#​6187: update vuln dependencies at 2026/07
#​6236: chore: bump stretch/testify pkg to remove old yaml dependencies
#​6248: build(deps): bump golang.org/x/text from 0.38.0 to 0.41.0
#​6249: build(deps): bump go.yaml.in/yaml/v2 from 2.4.2 to 2.4.4
#​6251: build(deps): bump github.com/go-errors/errors from 1.4.2 to 1.5.1
#​6254: build(deps): bump github.com/google/gnostic-models from 0.7.0 to 0.7.1
#​6255: build(deps): bump google.golang.org/protobuf from 1.36.11 to 1.36.12
#​6256: build(deps): bump golang.org/x/sys from 0.45.0 to 0.47.0
#​6266: build(deps): bump golang.org/x/text from 0.41.0 to 0.42.0
#​6267: build(deps): bump golang.org/x/sys from 0.47.0 to 0.48.0
#​6273: bump go-git, kin-openapi and k8s.io

chore

#​6190: chore: refactor read scheme to openapi from kubernetes api definition
#​6274: build: use the golangci-lint v2 with release binary
#​6305: Update kyaml to v0.21.2
#​6306: Update cmd/config to v0.21.2
#​6307: Update api to v0.21.2

pnpm/pnpm (pnpm)

v11.28.10: pnpm 11.28.10

Compare Source

pnpm 11.28.10 stops pnpm store prune from deleting other stores when cacheDir points to their parent directory. It also fixes globally installed commands that load hoisted dependencies, and repeat installs that missed changes to local dependencies.

Patch Changes
Installing packages
  • pnpm store prune preserves other stores and global package data when cacheDir points to their parent directory.

  • Commands installed with pnpm add --global now find the dependencies that pnpm hoists for their package. A package that loads a dependency it does not declare, such as a native addon's platform-specific package, failed with "Cannot find module". Reinstall such a package with pnpm add --global to update its existing command #​17503.

  • pnpm prune --prod no longer fails with ERR_PNPM_EXDEV when node_modules was copied from an earlier Docker build stage #​17424.

  • pnpm install now retries a Node.js runtime zip download when the connection drops partway through. A download that still fails names its URL. Before, a single dropped connection ended the install with terminated #​17411.

  • With the global virtual store, a change to a dependency of one package in a dependency cycle now gives every package in that cycle a new directory. Before, the other packages kept their directories and still linked the old copy of the changed package, so the project could load two copies of it #​17466.

    Packages in a dependency cycle, and packages that depend on one, move to new global virtual store directories once after this update. Those that run a build miss the side-effects cache once.

  • pnpm install and pnpm rebuild now refresh privately hoisted .bin shims in node_modules/.pnpm/node_modules/.bin after a dependency build replaces a script target with a native executable #​17402.

  • The Node.js latest selector now chooses the newest stable release #​17490.

  • The standalone @pnpm/exe builds now embed Node.js 26.13.0.

Repeat installs and lockfiles
  • pnpm install now resolves a local directory again after its package.json changes when an override or a package extension adds it to the dependencies of a registry package. pnpm install --frozen-lockfile fails on a lockfile that still records the old dependencies of such a directory #​17486.

  • With injectWorkspacePackages and per-project lockfiles, pnpm install now updates a project's lockfile when a local tarball that an injected workspace project depends on is replaced. The project's lockfile kept the old version and integrity before.

  • pnpm install now detects a change to a local tarball or directory that only a pnpmfile readPackage hook depends on. A repeat install reported "Already up to date" and kept the old contents before pnpm/tasks#227.

  • pnpm install now relinks a workspace: or link: dependency whose link was deleted from node_modules. It used to report "Already up to date" and leave the link missing #​17485.

  • Merging git branch lockfiles now keeps a workspace project whose directory is named __proto__. It was dropped from the merged lockfile before pnpm/tasks#59.

Adding and publishing packages
  • pnpm add no longer rewrites a catalog entry set to the dist-tag that the dependency resolves through. For example, an entry beta stays beta after pnpm add foo@beta or pnpm add foo. Before, the entry was replaced with the version the tag pointed to pnpm/tasks#225.

  • pnpm pack and pnpm publish now always include the binary file declared by a string bin field in package.json, even when files or .npmignore would otherwise exclude it.

  • When the version or range given to pnpm unpublish matches every published version, the error now says so and shows the same command with --force. It suggested running pnpm unpublish <pkg>@<version>, the command that had just failed.

Running commands
  • Every command, including pnpm --version, pnpm self-update, and invocations with unknown flags, now applies the same packageManager and devEngines.packageManager settings when switching to the pinned pnpm version or recording it in pnpm-lock.yaml. --config.<key> flags and lockfileDir now reach the version switch and lockfile sync on every entry point. Unreadable settings in pnpm-workspace.yaml or the global config.yaml that do not affect the pin decision no longer block the version switch pnpm/tasks#222.

  • On Windows, the shell shim of a .cmd or .bat bin now runs it under Git Bash when MSYS argument conversion is off, such as with MSYS_NO_PATHCONV=1 or MSYS2_ARG_CONV_EXCL='*'. The shim used to start an interactive cmd.exe prompt #​17480.

  • pnx and pnpm create now run the command in the directory selected by --dir or --workspace-root. Without either flag, the command still runs in the directory pnpm was started in.

  • The error for a dependency with an invalid name in a project's manifest now names the project's directory. It used to say only "The current package", which did not tell which workspace project to fix #​17475.

Platinum Sponsors

Bit OpenAI Notion
CodeRabbit Cloudflare

Gold Sponsors

Sanity Discord Vite
SerpApi Stackblitz Workleap
Nx Latitude Syntax

v11.28.9: pnpm 11.28.9

Compare Source

This release fixes a crash on registry responses with too many content encodings (GHSA-xjj6-f33q-929c) and sizes the install worker pool by the container's CPU quota. A repeat pnpm install now acts on more setting changes.

Patch Changes
Crashes and security
  • A registry response with too many content encodings can no longer crash pnpm. pnpm now uses undici 7.30.1, which fixes GHSA-xjj6-f33q-929c.

  • pnpm install now sizes its worker pool by the CPU quota of the container it runs in, such as a Kubernetes CPU limit, when that quota is smaller than the number of CPUs the container may run on. The default workspaceConcurrency respects the quota the same way. On a CI runner with a 4-CPU quota and hundreds of host CPUs, pnpm started hundreds of workers and ran out of memory #​17382.

Repeat installs and changed settings
  • A repeat pnpm install now acts on a change to these settings. Before, it reported "Already up to date".

    • storeDir or virtualStoreDir: it recreates node_modules.
    • virtualStoreDirMaxLength: it renames the virtual store directories.
    • dangerouslyAllowAllBuilds turned on: it runs the builds it skipped.
    • trustLockfile turned off: it verifies the lockfile.
  • pnpm add, pnpm remove, and pnpm update now fail when the node-linker setting differs from the one recorded in node_modules. A pnpm install of the whole workspace recreates node_modules with the new node-linker, and an install filtered to some projects fails pnpm/tasks#203.

  • An install filtered to some workspace projects now fails if node_modules was installed with a different nodeLinker, hoistPattern, publicHoistPattern, store, or virtual store. Before, it recreated node_modules and left the projects it skipped without their dependencies. A pnpm install of the whole workspace still recreates node_modules pnpm/tasks#217.

  • pnpm install now takes its fast path in a workspace with patchedDependencies when the previous install ran with another major version of pnpm.

  • pnpm install now relinks the bins of a workspace package when its bin field changes, including with --frozen-lockfile and an unchanged lockfile. A filtered install relinks them in the selected projects, and the next install that covers the remaining projects relinks them there #​17324.

  • pnpm install now removes command shims from node_modules/.bin when a workspace dependency renames or removes an entry from its bin field pnpm/tasks#211.

  • With nodeLinker: hoisted, an install that stops partway no longer leaves the next install trusting the packages it was replacing. Before, reverting the change that started the stopped install, such as a patch edit, kept the half-replaced package in node_modules.

  • pnpm run and pnpm exec no longer report the dependencies as out of date after a lockfile change when dedupePeers is true #​17322.

Resolving dependencies and the lockfile
  • A package that a plain range and a <prefix>: specifier both resolve from one registry is now recorded once in pnpm-lock.yaml and installed once. The lockfile key names the registry a package resolved from. When that registry declares a prefix, through prefix in registries or through namedRegistries, the package is keyed <name>@<prefix>:<version> however its dependency was written: with the prefix, as a plain range its scope routes to that registry, or through the default registry. Before, the plain range was keyed <name>@<version>, so one tarball was installed twice and instanceof checks and module singletons broke between the two copies. The same name and version served by two registries still get separate entries. When several prefixes declare one registry, its packages are keyed by the lexicographically smallest prefix.

    If a scope you route reaches a registry that also declares a prefix, your next pnpm install re-keys those entries, which shows up as a lockfile diff. Commit it. pnpm install --frozen-lockfile installs the lockfile as recorded.

  • pnpm install now resolves a scope's packages again when the scope is routed to another registry in registries. Before, the lockfile kept the versions and integrity resolved from the old registry, so the install failed when the new registry did not serve a locked version or served different content. pnpm records in the workspace state which registry each scope routed to, so a fresh clone without that record installs the lockfile as recorded. Changing the default registry resolves nothing again, and pnpm install --frozen-lockfile is unchanged.

  • An optional dependency written with a named-registry prefix, such as work:^1.0.0, now fails the install when it cannot be resolved but the lockfile already has a matching entry from that registry. Such a dependency was skipped, which removed its entries from the lockfile.

  • With injectWorkspacePackages: true, a workspace: dependency written as a relative path, such as workspace:../lib-a, in a workspace package now resolves from that package's directory #​17284.

  • Fixed pnpm install failing with ERR_PNPM_UNSUPPORTED_PROTOCOL when a workspace package injected through a relative path, such as workspace:../lib, has catalog: dependencies. Their catalog entries now resolve the way they do for a package injected by name #​17280.

  • pnpm install now applies the serverType registry setting when it updates the lockfile for an override or catalog change without a full resolution. pnpm wrote the tarball URLs of a declared registry into the lockfile in that case.

  • Added the pnpr value to the serverType registry setting. pnpm leaves the tarball URLs of a pnpr registry out of pnpm-lock.yaml.

  • A registries entry whose prefix is __proto__ is no longer ignored.

  • Installs delegated to a pnpr server now resolve every prefix declared for a registry URL. A dependency or lockfile entry that used the second of two prefixes for the same registry, such as zeta: next to work: in namedRegistries, failed on the server pnpm/tasks#204.

Registries, proxies, and downloading pnpm
  • The proxy settings httpProxy, httpsProxy, noProxy, proxy, and noproxy set in the global config.yaml, through PNPM_CONFIG_HTTPS_PROXY and the matching variables, or as --config.httpsProxy on the command line now apply to pnpm self-update and to the download of the pnpm version pinned in packageManager. Previously, these requests read the proxy only from .npmrc and the HTTPS_PROXY family of variables pnpm/tasks#215.

  • When https-proxy is false, pnpm now downloads the pnpm version pinned by packageManager through the legacy proxy setting, as installs already do. Setting proxy to false now also stops that download from using the HTTP_PROXY environment variable. The signature check of the pinned pnpm now uses the same proxy and TLS settings as its download pnpm/tasks#193.

  • strictSsl and localAddress set in the global config.yaml, through PNPM_CONFIG_STRICT_SSL and PNPM_CONFIG_LOCAL_ADDRESS, or on the command line now apply to pnpm self-update and to the download of the pnpm version pinned in packageManager. These requests read them from .npmrc only before. --config.localAddress now reaches them in the camelCase spelling too pnpm/tasks#201.

Commands
  • pnpm audit --ignore and pnpm audit --ignore-unfixable now exit with a non-zero code when vulnerabilities at or above the audit level remain after ignoring. Before, these commands always exited with code 0.

  • pnpm audit --fix and pnpm audit --interactive now fail with ERR_PNPM_AUDIT_FIX_WITH_IGNORE when combined with --ignore or --ignore-unfixable. Before, the fix ran and the ignore flags had no effect.

  • pnpm ci --lockfile and pnpm ci --config.lockfile=true no longer delete pnpm-lock.yaml. pnpm ci now always keeps the lockfile and runs a frozen install from it.

  • pnpm deploy now keeps a deployed symlink to a directory inside the project even if the directory is not among the deployed files, such as a link into node_modules #​17288.

  • pnpm pack and pnpm publish again include the files of a publishConfig.directory that is reached through a symlink, together with its bundled dependencies #​17390.

  • pnpm -r publish --batch now sends PUT /-/pnpr/v0/publish, the batch publish endpoint that pnpr serves.

  • pnpm store prune now keeps the packages that a project still uses when pnpm copied or cloned them into node_modules. These include patched packages, built packages, and every package installed with packageImportMethod: copy. Before, the prune removed them, and the next install downloaded them again #​7192.

  • pnpm store prune now keeps the packages of a project that was installed with a different symlinked spelling of the store path. Previously, prune dropped such a project from its list and removed the packages only that project used from the global virtual store.

Speed and output
  • Sped up installs of projects whose local directory dependencies share transitive local directory dependencies. pnpm no longer checks a shared directory again for each direct dependency that reaches it #​17374.

  • Output that fills the terminal, such as pnpm run --stream script output, is now written once. Before, every new line also rewrote all the lines already on screen #​17387.

  • The warning about unrecognized settings now marks symlinkedLockfileTargetDirs as a setting of a newer pnpm version.

Platinum Sponsors

Bit OpenAI Notion
CodeRabbit

Gold Sponsors

Sanity Discord Vite
SerpApi Stackblitz Workleap
Nx Latitude

v11.28.8: pnpm 11.28.8

Compare Source

Patch Changes
  • The standalone @pnpm/exe builds now embed Node.js 26.12.1. The previously embedded Node.js 26.0.0 still trusted the certificate authority intermediates that Node.js distrusted in October 2026, so a standalone pnpm accepted TLS certificates issued under them.

Platinum Sponsors

Bit OpenAI Notion

[!IMPORTANT]✂ PR body was truncated to here.


Configuration

📅 Schedule: (in timezone Asia/Tokyo)

  • Branch creation
    • On day 1 of the month (* * 1 * *)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@coderabbitai

coderabbitai Bot commented Oct 31, 2026

Copy link
Copy Markdown

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

Run configuration
  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 83c1cca1-05ab-46b0-9123-9fbb038088d4

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@github-actions

Copy link
Copy Markdown
Contributor

Preview (prod backend + PR dashboard) → https://1462.ns-preview.trapti.tech/

@pirosiki197
pirosiki197 merged commit 931c994 into main Nov 1, 2026
19 checks passed
@pirosiki197
pirosiki197 deleted the renovate/mise-tools branch November 1, 2026 09:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant