Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

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

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 18, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@actions/core (source) ^1.10.0 -> ^1.11.1 age adoption passing confidence
@antfu/ni ^0.20.0 -> ^0.23.2 age adoption passing confidence
@types/node (source) ^18.15.5 -> ^18.19.76 age adoption passing confidence
@types/semver (source) ^7.3.13 -> ^7.5.8 age adoption passing confidence
execa ^7.1.1 -> ^7.2.0 age adoption passing confidence
node-fetch ^3.3.1 -> ^3.3.2 age adoption passing confidence
pnpm (source) 10.0.0 -> 10.4.1 age adoption passing confidence
semver ^7.3.8 -> ^7.7.1 age adoption passing confidence
simple-git-hooks ^2.8.1 -> ^2.11.1 age adoption passing confidence
tsx (source) ^4.19.2 -> ^4.19.3 age adoption passing confidence

Release Notes

antfu-collective/ni (@​antfu/ni)

v0.23.2

Compare Source

No significant changes

    View changes on GitHub

v0.23.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.23.0

Compare Source

   🚨 Breaking Changes
    View changes on GitHub

v0.22.4

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.22.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.22.2

Compare Source

No significant changes

    View changes on GitHub

v0.22.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.22.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.12

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.21.11

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.21.10

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.21.9

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.8

Compare Source

   🚀 Features
    View changes on GitHub

v0.21.7

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.6

Compare Source

   🚀 Features
    View changes on GitHub

v0.21.5

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v0.21.4

Compare Source

   🚀 Features
    View changes on GitHub

v0.21.3

Compare Source

No significant changes

    View changes on GitHub

v0.21.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v0.21.1

Compare Source

v0.21.0

Compare Source

   🚨 Breaking Changes
   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub
pnpm/pnpm (pnpm)

v10.4.1

Compare Source

Patch Changes
  • Throws an error when the value provided by the --allow-build option overlaps with the pnpm.ignoredBuildDependencies list #​9105.
  • Print pnpm's version after the execution time at the end of the console output.
  • Print warning about ignored builds of dependencies on repeat install #​9106.
  • Setting init-package-manager should work.

v10.4.0

Compare Source

Minor Changes

  • pnpm approve-builds --global works now for allowing dependencies of globally installed packages to run postinstall scripts.

  • The pnpm add command now supports a new flag, --allow-build, which allows building the specified dependencies. For instance, if you want to install a package called bundle that has esbuild as a dependency and want to allow esbuild to run postinstall scripts, you can run:

    pnpm --allow-build=esbuild add bundle

    This will run esbuild's postinstall script and also add it to the pnpm.onlyBuiltDependencies field of package.json. So, esbuild will always be allowed to run its scripts in the future.

    Related PR: #​9086.

  • The pnpm init command adds a packageManager field with the current version of pnpm CLI #​9069. To disable this behaviour, set the init-package-manager setting to false.

Patch Changes
  • pnpm approve-builds should work after two consecutive pnpm install runs #​9083.
  • Fix instruction for updating pnpm with corepack #​9101.
  • The pnpm version specified by packageManager cannot start with v.

v10.3.0

Compare Source

Minor Changes
  • Added a new setting called strict-dep-builds. When enabled, the installation will exit with a non-zero exit code if any dependencies have unreviewed build scripts (aka postinstall scripts) #​9071.
Patch Changes
  • Fix a false negative of verify-deps-before-run after pnpm install --production|--no-optional #​9019.
  • Print the warning about blocked installation scripts at the end of the installation output and make it more prominent.

v10.2.1

Compare Source

Patch Changes
  • Don't read a package from side-effects cache if it isn't allowed to be built #​9042.
  • pnpm approve-builds should work, when executed from a subdirectory of a workspace #​9042.
  • pnpm deploy --legacy should work without injected dependencies.
  • Add information about how to deploy without "injected dependencies" to the "pnpm deploy" error message.

v10.2.0

Compare Source

Minor Changes

  • Packages executed via pnpm dlx and pnpm create are allowed to be built (run postinstall scripts) by default.

    If the packages executed by dlx or create have dependencies that have to be built, they should be listed via the --allow-build flag. For instance, if you want to run a package called bundle that has esbuild in dependencies and want to allow esbuild to run postinstall scripts, run:

    pnpm --allow-build=esbuild dlx bundle

    Related PR: #​9026.

Patch Changes
  • Quote args for scripts with shell-quote to support new lines (on POSIX only) #​8980.
  • Fix a bug in which pnpm deploy fails to read the correct projectId when the deploy source is the same as the workspace directory #​9001.
  • Proxy settings should be respected, when resolving Git-hosted dependencies #​6530.
  • Prevent overrides from adding invalid version ranges to peerDependencies by keeping the peerDependencies and overriding them with prod dependencies #​8978.
  • Sort the package names in the "pnpm.onlyBuiltDependencies" list saved by pnpm approve-builds.

v10.1.0

Compare Source

Minor Changes
  • Added a new command for printing the list of dependencies with ignored build scripts: pnpm ignored-builds #​8963.
  • Added a new command for approving dependencies for running scripts during installation: pnpm approve-builds #​8963.
  • Added a new setting called optimistic-repeat-install. When enabled, a fast check will be performed before proceeding to installation. This way a repeat install or an install on a project with everything up-to-date becomes a lot faster. But some edge cases might arise, so we keep it disabled by default for now #​8977.
  • Added a new field "pnpm.ignoredBuiltDependencies" for explicitly listing packages that should not be built. When a package is in the list, pnpm will not print an info message about that package not being built #​8935.
Patch Changes
  • Verify that the package name is valid when executing the publish command.
  • When running pnpm install, the preprepare and postprepare scripts of the project should be executed #​8989.
  • Allow workspace: and catalog: to be part of wider version range in peerDependencies.
  • pnpm deploy should inherit the pnpm object from the root package.json #​8991.
  • Make sure that the deletion of a node_modules in a sub-project of a monorepo is detected as out-of-date #​8959.
  • Fix infinite loop caused by lifecycle scripts using pnpm to execute other scripts during pnpm install with verify-deps-before-run=install #​8954.
  • Replace strip-ansi with the built-in util.stripVTControlCharacters #​9009.
  • Do not print patched dependencies as ignored dependencies that require a build #​8952.
npm/node-semver (semver)

v7.7.1

Compare Source

Bug Fixes
privatenumber/tsx (tsx)

v4.19.3

Compare Source

Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 8df1e2b to a4aed74 Compare November 23, 2024 11:24
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from b2534da to 0374365 Compare November 29, 2024 03:01
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0374365 to d93131a Compare December 11, 2024 16:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from d93131a to 03446e5 Compare December 22, 2024 08:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 8622a05 to d906770 Compare January 6, 2025 23:44
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 334ffdf to 59b1346 Compare January 23, 2025 07:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 791bf55 to 88ad81f Compare January 31, 2025 07:40
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 66c68e5 to 55b0982 Compare February 2, 2025 10:16
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Feb 2, 2025 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: pnpm-lock.yaml
 ERR_PNPM_UNSUPPORTED_ENGINE  Unsupported environment (bad pnpm and/or Node.js version)

Your pnpm version is incompatible with "/tmp/renovate/repos/github/rspack-contrib/rsbuild-ecosystem-ci".

Expected version: 10.0.0
Got: 10.4.1

This is happening because the package's manifest has an engines.pnpm field specified.
To fix this issue, install the required pnpm version globally.

To install the latest version of pnpm, run "pnpm i -g pnpm".
To check your pnpm version, run "pnpm -v".

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 822ca28 to 10eed02 Compare February 6, 2025 21:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from fd5d30c to 67e3529 Compare February 17, 2025 02:38
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 67e3529 to 13563ec Compare February 19, 2025 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants