Skip to content

fix corepack detection for package manager version determination#11596

Merged
kodiakhq[bot] merged 9 commits intomainfrom
endangeredmassa/fix-corepack-detection
May 15, 2024
Merged

fix corepack detection for package manager version determination#11596
kodiakhq[bot] merged 9 commits intomainfrom
endangeredmassa/fix-corepack-detection

Conversation

@EndangeredMassa
Copy link
Contributor

@EndangeredMassa EndangeredMassa commented May 14, 2024

The previous logic was checking for the env var ENABLE_EXPERIMENTAL_COREPACK to determine if corepack was being used by a project. However, this value only means that the build system should consider corepack, not that it's actively being used.

We need to check that flag AND the existence of a packageManager property in the project's package.json.

@changeset-bot
Copy link

changeset-bot bot commented May 14, 2024

🦋 Changeset detected

Latest commit: bd57cf3

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 7 packages
Name Type
@vercel/build-utils Minor
vercel Patch
@vercel/client Patch
@vercel/gatsby-plugin-vercel-builder Patch
@vercel/node Patch
@vercel/static-build Patch
@vercel-internals/types Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

trek
trek previously approved these changes May 14, 2024
@EndangeredMassa
Copy link
Contributor Author

I'm updating this to include the actual fix, not just the logging fix.

erikareads
erikareads previously approved these changes May 15, 2024
@kodiakhq kodiakhq bot merged commit ccd7eb1 into main May 15, 2024
@kodiakhq kodiakhq bot deleted the endangeredmassa/fix-corepack-detection branch May 15, 2024 19:25
EndangeredMassa pushed a commit that referenced this pull request May 15, 2024
This PR was opened by the [Changesets
release](https://github.com/changesets/action) GitHub action. When
you're ready to do a release, you can merge this and the packages will
be published to npm automatically. If you're not ready to do a release
yet, that's fine, whenever you add more changesets to main, this PR will
be updated.


# Releases
## @vercel/build-utils@8.2.0

### Minor Changes

- fix corepack detection for package manager version determination
([#11596](#11596))

### Patch Changes

- Fix triggering of ignored project settings node version warning
([#11550](#11550))

## vercel@34.2.0

### Minor Changes

- Stop sending system environment variables in dev
([#11526](#11526))

### Patch Changes

- Updated dependencies
\[[`d3c1267e2`](d3c1267),
[`ccd7eb1fb`](ccd7eb1)]:
    -   @vercel/build-utils@8.2.0
    -   @vercel/node@3.1.5
    -   @vercel/static-build@2.5.9

## @vercel/client@13.2.7

### Patch Changes

- Updated dependencies
\[[`d3c1267e2`](d3c1267),
[`ccd7eb1fb`](ccd7eb1)]:
    -   @vercel/build-utils@8.2.0

## @vercel/gatsby-plugin-vercel-builder@2.0.31

### Patch Changes

- Updated dependencies
\[[`d3c1267e2`](d3c1267),
[`ccd7eb1fb`](ccd7eb1)]:
    -   @vercel/build-utils@8.2.0

## @vercel/node@3.1.5

### Patch Changes

- Updated dependencies
\[[`d3c1267e2`](d3c1267),
[`ccd7eb1fb`](ccd7eb1)]:
    -   @vercel/build-utils@8.2.0

## @vercel/static-build@2.5.9

### Patch Changes

-   Updated dependencies \[]:
    -   @vercel/gatsby-plugin-vercel-builder@2.0.31

## @vercel-internals/types@1.0.36

### Patch Changes

- Updated dependencies
\[[`d3c1267e2`](d3c1267),
[`ccd7eb1fb`](ccd7eb1)]:
    -   @vercel/build-utils@8.2.0

Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
@AurelienGasser
Copy link

This PR may have introduced a regression: #11607

@wweaver
Copy link

wweaver commented May 17, 2024

@EndangeredMassa, with #11607 is that going to take any priority? Or no since corepack is still considered experimental in Vercel's docs https://vercel.com/changelog/corepack-experimental-is-now-available.

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.

5 participants