fix: bump non-breaking dependencies to latest - #653
Merged
Conversation
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
1 participant
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.
Automated non-major dependency bump (deps-train).
package.json
Transitive refresh (
pnpm update) — 1 package(s) movedShow transitive changes
What changed
pnpm11.21.0 → 11.22.0pnpm 11.22
Minor Changes
Added
pnpm cache path, which prints the directory pnpm uses for its metadata cache. CI setups can use it to cache that directory — including the lockfile verification log, which lets a job skip re-checking an unchanged lockfile against the configured supply-chain policies.--config.config-dirno longer reaches the config through a project'spnpm-workspace.yaml, and neither do the--config.spellings of the other settings a project manifest may no longer contribute (--config.pnpm-home-dir,--config.workspace-dir,--config.global-pkg-dir,--config.root-project-manifest-dir). None of them was ever a supported way to set those directories: pnpm resolves them from the environment, and these flags took effect only because the project-manifest merge re-applied the command line afterwards. The dedicated flags, such as--dirand--global-dir, are unaffected #13629.pnpm config setrefuses to write a setting to a project'spnpm-workspace.yamlthat pnpm does not read from there, rather than leaving a key in the file that does nothing. Those settings areconfigDir,pnpmHomeDir,stateDirand the others that name machine-level state. The command fails withERR_PNPM_CONFIG_SET_NOT_A_PROJECT_SETTING, naming where the setting does belong when it belongs somewhere.pnpm config deletestill clears one that a file already carries, in whichever spelling it uses [#13629](https://github.co…notes truncated.
compare 11.21.0…11.22.0 · npm