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>

…12358)

In #11526 we stopped pulling down
environment variables that are set by the runtime into `.env` files
since this really is an appropriate location for them and blank values
can cause issues for some customers.

However, we were relying on these so that `vercel dev` had a similar set
of variables as the platform at runtime. Losing these was a breaking
change.

This PR sets them within the development sever itself to better simulate
our actual runtime environment. I wasn't quite sure of the use of
`projectSettings?.autoExposeSystemEnvs`
[here](https://github.com/vercel/vercel/blob/804b94fa6177198728b1d6cd497aad787b452130/packages/cli/src/util/dev/server.ts#L709-L711)
and potentially the correct location for these is within that `if`
block?

Closes #2878

---------

Co-authored-by: Nathan Rajlich <n@n8.io>

…12358)

In vercel/vercel#11526 we stopped pulling down
environment variables that are set by the runtime into `.env` files
since this really is an appropriate location for them and blank values
can cause issues for some customers.

However, we were relying on these so that `vercel dev` had a similar set
of variables as the platform at runtime. Losing these was a breaking
change.

This PR sets them within the development sever itself to better simulate
our actual runtime environment. I wasn't quite sure of the use of
`projectSettings?.autoExposeSystemEnvs`
[here](https://github.com/vercel/vercel/blob/9537e8c1eb2428e76c8ccf3a52c2e7e8de42e96a/packages/cli/src/util/dev/server.ts#L709-L711)
and potentially the correct location for these is within that `if`
block?

Closes #2878

---------

Co-authored-by: Nathan Rajlich <n@n8.io>