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

nx-remote-cache reuses the ENV from the intial build #23

Open
Kyoss79 opened this issue Feb 7, 2024 · 0 comments
Open

nx-remote-cache reuses the ENV from the intial build #23

Kyoss79 opened this issue Feb 7, 2024 · 0 comments

Comments

@Kyoss79
Copy link

Kyoss79 commented Feb 7, 2024

Which package / area of the repo does the bug impact?

No response

What version are you using?

@vercel/[email protected]

What package manager are you using / does the bug impact?

npm, pnpm, Yarn v1, Yarn v2/v3

What operating system are you using?

Mac

Describe the Bug

As stated above.
Building a project on develop and then committing that branch to main
makes vercel reuse the existing build,
with existing ENV variables from the other environment.

This might be the intended behaviour but a heads-up warning on your documentation would be nice indeed.

Expected Behavior

Inform users about this behaviour

To Reproduce

Build

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

No branches or pull requests

1 participant