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.

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

feat: update package manager versions #348

Merged
merged 4 commits into from
Jan 13, 2024
Merged

Conversation

github-actions[bot]
Copy link
Contributor

@github-actions github-actions bot commented Jan 5, 2024

This is an automated update of package manager versions

@@ -38,7 +38,7 @@
}
},
"pnpm": {
"default": "8.13.1+sha1.90f9b2bb3ed58632bcb7b13c3902d6873ee9501c",
"default": "8.14.1+sha1.d039b38e0b20ad012ed548e44267b8d4c88b447a",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this config still used?

I thought that corepack doesn't pin the global version of package managers anymore and instead fetches the latest?

Copy link
Contributor

@aduh95 aduh95 Jan 13, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's used when the environment has disabled the auto lookup:

corepack/README.md

Lines 222 to 224 in 9bee415

- `COREPACK_DEFAULT_TO_LATEST` can be set to `0` in order to instruct Corepack
not to lookup on the remote registry for the latest version of the selected
package manager.

@aduh95 aduh95 enabled auto-merge (squash) January 13, 2024 00:50
@aduh95 aduh95 merged commit cc3ada7 into main Jan 13, 2024
9 of 10 checks passed
@aduh95 aduh95 deleted the actions/tools-update-config.json branch January 13, 2024 01:04
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.

3 participants