Repository navigation
chore(deps): update mise tools - #1462
Merged
Merged
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Contributor
|
Preview (prod backend + PR dashboard) → https://1462.ns-preview.trapti.tech/ |
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:
1.73.0→1.75.03.11.26→3.11.292.14.0→2.15.04.3.0→4.3.11.37.1→1.37.25.8.1→5.8.311.27.0→11.28.10Release Notes
bufbuild/buf (buf)
v1.75.0Compare Source
buf builddroppingmessage_set_wire_format,weakfield options, and MessageSetextensions, and truncating MessageSet extension ranges, when a file has an unused import.
such as
'\x95'in a protovalidate rule.BUF_DEBUG,BUF_LOG_FORMAT, andBUF_TIMEOUTenvironment variables as defaults for the--debug,--log-format, and--timeoutglobal flags. Flags take precedence when set.import optionsyntax inedition 2024 and later.
cc_enable_arenasfor edition 2026 files, where the option wasremoved.
buf convertandbuf curlignoring the(pb.enumvalue.json).stringoption for enumvalue JSON names.
v1.74.0Compare Source
PROTOVALIDATElint rule, which is now up to 3x fasterand allocates less memory on modules using
celrules orexamplevalues.FileDescriptor.ModuleName()in bufplugin-go v0.11.0 and later.buf curlto automatically use HTTP/2 prior knowledge forhttpURLs when serverreflection, the gRPC protocol, or a bidirectional streaming method is used, since all of these
require HTTP/2. The
--http2-prior-knowledgeflag is no longer required in these cases.--stdin-filepathflag tobuf format, which reads a single.protofile fromstdin and writes the formatted result to stdout. The path is not read from disk, and is
only used to report parse errors and diffs.
buf convertpanic when converting images that contain files without asyntaxdeclaration or with unused imports.
buf generatewithstrategy: directoryandinclude_imports: trueadding importsto the
CodeGeneratorRequestof the directory that imports them. Imports are now splitby directory into their own requests, the same as non-imports.
!, such asignore: [!foo/bar.proto]. Previously they parsed as empty strings, now they rejectedwith an error.
groupfields being ignored.buf.go.gen.yamlandbuf.gen.go.yaml.buf curlerror message for methods that accept a single request message.--configflag tobuf lsp serveto use abuf.yamlfile or data in place ofdiscovering
buf.yamlfiles. Workspaces are resolved from the editor's root folder.inputsin abuf.gen.yamlthat resolve to the same archive, git repository, or imageare fetched once instead of once per input.
STRICTdefault symbol visibility, andsource locations of
export/localtypes.sqldef/sqldef (go:github.com/sqldef/sqldef/v3/cmd/mysqldef)
v3.11.29Compare Source
v3.11.28Compare Source
v3.11.27Compare Source
golangci/golangci-lint (golangci-lint)
v2.15.0Compare Source
Released on 2026-10-16
errcheck: from 1.20.0 to 1.30.0exhaustive: from 0.13.0 to 0.15.0 (gocognit: from 1.2.1 to 1.3.0golines: from 0.15.0 to 0.16.0govet-modernize: from 0.50.0 to 0.52.0loggercheck: from 0.12.0 to 0.13.0predeclared: from 0.2.2 to 0.3.0wrapcheck: from 2.12.0 to 2.13.0bidichk: from 0.3.3 to 0.3.4canonicalheader: froma25c71ctoe18e5c5gofumpt: improve deprecation logsgosec: improve concurrency default valueiface: from 1.5.1 to 1.5.3paralleltest: from 1.0.15 to 1.0.16revive: from 1.17.0 to 1.17.1revive: the rulescontext-keys-type,errorf,modifies-value-receiver,range-val-address,string-of-int,time-equal,time-naming,unexported-return,unhandled-error,var-declarationare working (less randomly).rowserrcheck: fromc5f79b8toe0740d5staticcheck: from 0.8.1 to 0.8.2revive)exhaustivelinter:explicit-exhaustive-switchandexplicit-exhaustive-maphave been replaced byexplicit-exhaustive.checkthe valuemaphas been replaced bymapliteral.ignore-enum-members(string) has been replaced byignore-constants(slice).ignore-enum-types(string) has been replaced byignore-types(slice).helm/helm (helm)
v4.3.1: Helm v4.3.1Compare 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!
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 1155and can be found at @scottrigby keybase account. Please use the attached signatures for verifying this release usinggpg.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
Changelog
c0d08d0(Terry Howe)0c0146e(dependabot[bot])dd91731(Terry Howe)3a376b2(Ruslan Shaydullin)5fed6a5(Pujitha Paladugu)b227bf4(dependabot[bot])af79b8e(dependabot[bot])ab6b245(dependabot[bot])0f20617(dependabot[bot])e26e158(dependabot[bot])23ab1c5(dependabot[bot])8303180(dependabot[bot])kubernetes/kubernetes (kubectl)
v1.37.2Compare Source
See kubernetes-announce@. Additional binary downloads are linked in the CHANGELOG.
See the CHANGELOG for more details.
kubernetes-sigs/kustomize (kustomize)
v5.8.3Compare 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.2Compare Source
Introduction
In this release, we implemented refactoring to update dependencies and add new features.
This release adds the
kustomize edit add configurationandkustomize edit remove componentcommands. #6037 #6083The 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 buildis 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.10Compare Source
pnpm 11.28.10 stops
pnpm store prunefrom deleting other stores whencacheDirpoints 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 prunepreserves other stores and global package data whencacheDirpoints to their parent directory.Commands installed with
pnpm add --globalnow 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 withpnpm add --globalto update its existing command #17503.pnpm prune --prodno longer fails withERR_PNPM_EXDEVwhennode_moduleswas copied from an earlier Docker build stage #17424.pnpm installnow 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 withterminated#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 installandpnpm rebuildnow refresh privately hoisted.binshims innode_modules/.pnpm/node_modules/.binafter a dependency build replaces a script target with a native executable #17402.The Node.js
latestselector now chooses the newest stable release #17490.The standalone
@pnpm/exebuilds now embed Node.js 26.13.0.Repeat installs and lockfiles
pnpm installnow resolves a local directory again after itspackage.jsonchanges when an override or a package extension adds it to the dependencies of a registry package.pnpm install --frozen-lockfilefails on a lockfile that still records the old dependencies of such a directory #17486.With
injectWorkspacePackagesand per-project lockfiles,pnpm installnow 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 installnow detects a change to a local tarball or directory that only a pnpmfilereadPackagehook depends on. A repeat install reported "Already up to date" and kept the old contents before pnpm/tasks#227.pnpm installnow relinks aworkspace:orlink:dependency whose link was deleted fromnode_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 addno longer rewrites a catalog entry set to the dist-tag that the dependency resolves through. For example, an entrybetastaysbetaafterpnpm add foo@betaorpnpm add foo. Before, the entry was replaced with the version the tag pointed to pnpm/tasks#225.pnpm packandpnpm publishnow always include the binary file declared by a stringbinfield inpackage.json, even whenfilesor.npmignorewould otherwise exclude it.When the version or range given to
pnpm unpublishmatches every published version, the error now says so and shows the same command with--force. It suggested runningpnpm 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 samepackageManageranddevEngines.packageManagersettings when switching to the pinned pnpm version or recording it inpnpm-lock.yaml.--config.<key>flags andlockfileDirnow reach the version switch and lockfile sync on every entry point. Unreadable settings inpnpm-workspace.yamlor the globalconfig.yamlthat do not affect the pin decision no longer block the version switch pnpm/tasks#222.On Windows, the shell shim of a
.cmdor.batbin now runs it under Git Bash when MSYS argument conversion is off, such as withMSYS_NO_PATHCONV=1orMSYS2_ARG_CONV_EXCL='*'. The shim used to start an interactive cmd.exe prompt #17480.pnxandpnpm createnow run the command in the directory selected by--diror--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
Gold Sponsors
v11.28.9: pnpm 11.28.9Compare 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 installnow 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 installnow 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 defaultworkspaceConcurrencyrespects 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 installnow acts on a change to these settings. Before, it reported "Already up to date".storeDirorvirtualStoreDir: it recreatesnode_modules.virtualStoreDirMaxLength: it renames the virtual store directories.dangerouslyAllowAllBuildsturned on: it runs the builds it skipped.trustLockfileturned off: it verifies the lockfile.pnpm add,pnpm remove, andpnpm updatenow fail when thenode-linkersetting differs from the one recorded innode_modules. Apnpm installof the whole workspace recreatesnode_moduleswith the newnode-linker, and an install filtered to some projects fails pnpm/tasks#203.An install filtered to some workspace projects now fails if
node_moduleswas installed with a differentnodeLinker,hoistPattern,publicHoistPattern, store, or virtual store. Before, it recreatednode_modulesand left the projects it skipped without their dependencies. Apnpm installof the whole workspace still recreatesnode_modulespnpm/tasks#217.pnpm installnow takes its fast path in a workspace withpatchedDependencieswhen the previous install ran with another major version of pnpm.pnpm installnow relinks the bins of a workspace package when itsbinfield changes, including with--frozen-lockfileand 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 installnow removes command shims fromnode_modules/.binwhen a workspace dependency renames or removes an entry from itsbinfield 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 innode_modules.pnpm runandpnpm execno longer report the dependencies as out of date after a lockfile change whendedupePeersistrue#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 inpnpm-lock.yamland installed once. The lockfile key names the registry a package resolved from. When that registry declares a prefix, throughprefixinregistriesor throughnamedRegistries, 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 andinstanceofchecks 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 installre-keys those entries, which shows up as a lockfile diff. Commit it.pnpm install --frozen-lockfileinstalls the lockfile as recorded.pnpm installnow resolves a scope's packages again when the scope is routed to another registry inregistries. 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, andpnpm install --frozen-lockfileis 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, aworkspace:dependency written as a relative path, such asworkspace:../lib-a, in a workspace package now resolves from that package's directory #17284.Fixed
pnpm installfailing withERR_PNPM_UNSUPPORTED_PROTOCOLwhen a workspace package injected through a relative path, such asworkspace:../lib, hascatalog:dependencies. Their catalog entries now resolve the way they do for a package injected by name #17280.pnpm installnow applies theserverTyperegistry 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
pnprvalue to theserverTyperegistry setting. pnpm leaves the tarball URLs of a pnpr registry out ofpnpm-lock.yaml.A
registriesentry whoseprefixis__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 towork:innamedRegistries, failed on the server pnpm/tasks#204.Registries, proxies, and downloading pnpm
The proxy settings
httpProxy,httpsProxy,noProxy,proxy, andnoproxyset in the globalconfig.yaml, throughPNPM_CONFIG_HTTPS_PROXYand the matching variables, or as--config.httpsProxyon the command line now apply topnpm self-updateand to the download of the pnpm version pinned inpackageManager. Previously, these requests read the proxy only from.npmrcand theHTTPS_PROXYfamily of variables pnpm/tasks#215.When
https-proxyisfalse, pnpm now downloads the pnpm version pinned bypackageManagerthrough the legacyproxysetting, as installs already do. Settingproxytofalsenow also stops that download from using theHTTP_PROXYenvironment variable. The signature check of the pinned pnpm now uses the same proxy and TLS settings as its download pnpm/tasks#193.strictSslandlocalAddressset in the globalconfig.yaml, throughPNPM_CONFIG_STRICT_SSLandPNPM_CONFIG_LOCAL_ADDRESS, or on the command line now apply topnpm self-updateand to the download of the pnpm version pinned inpackageManager. These requests read them from.npmrconly before.--config.localAddressnow reaches them in the camelCase spelling too pnpm/tasks#201.Commands
pnpm audit --ignoreandpnpm audit --ignore-unfixablenow 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 --fixandpnpm audit --interactivenow fail withERR_PNPM_AUDIT_FIX_WITH_IGNOREwhen combined with--ignoreor--ignore-unfixable. Before, the fix ran and the ignore flags had no effect.pnpm ci --lockfileandpnpm ci --config.lockfile=trueno longer deletepnpm-lock.yaml.pnpm cinow always keeps the lockfile and runs a frozen install from it.pnpm deploynow keeps a deployed symlink to a directory inside the project even if the directory is not among the deployed files, such as a link intonode_modules#17288.pnpm packandpnpm publishagain include the files of apublishConfig.directorythat is reached through a symlink, together with its bundled dependencies #17390.pnpm -r publish --batchnow sendsPUT /-/pnpr/v0/publish, the batch publish endpoint that pnpr serves.pnpm store prunenow keeps the packages that a project still uses when pnpm copied or cloned them intonode_modules. These include patched packages, built packages, and every package installed withpackageImportMethod: copy. Before, the prune removed them, and the next install downloaded them again #7192.pnpm store prunenow 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 --streamscript 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
symlinkedLockfileTargetDirsas a setting of a newer pnpm version.Platinum Sponsors
Gold Sponsors
v11.28.8: pnpm 11.28.8Compare Source
Patch Changes
@pnpm/exebuilds 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
[!IMPORTANT]✂ PR body was truncated to here.
Configuration
📅 Schedule: (in timezone Asia/Tokyo)
* * 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 has been generated by Mend Renovate CLI.