Skip to content

Conversation

barbados-clemens
Copy link
Contributor

@barbados-clemens barbados-clemens commented May 3, 2025

  • fix(install-node): make sure to always install latest corepack
  • fix(install-node): make sure to match default pnpm version from base image
image

sometimes node versions of corepack comes with outdate key signatures.
this changes makes sure to always install the latest version of corepack
after updating node
…image

base image use pnpm v9, so default install pnpm v9 when installing new
node versions as well
@barbados-clemens barbados-clemens changed the title fix latest corepack fix(install-node): always install latest corepack version May 3, 2025
@barbados-clemens barbados-clemens self-assigned this May 3, 2025
@barbados-clemens barbados-clemens marked this pull request as ready for review May 3, 2025 23:07
@barbados-clemens
Copy link
Contributor Author

@barbados-clemens barbados-clemens merged commit fed180c into main May 3, 2025
1 check passed
@barbados-clemens barbados-clemens deleted the fix-latest-corepack branch May 3, 2025 23:24
github-actions bot pushed a commit that referenced this pull request May 3, 2025
* fix(install-node): make sure to always install latest corepack

sometimes node versions of corepack comes with outdate key signatures.
this changes makes sure to always install the latest version of corepack
after updating node

* fix(install-node): make sure to match default pnpm version from base image

base image use pnpm v9, so default install pnpm v9 when installing new
node versions as well
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.

2 participants