ci: define the CI env var when running in CI #137
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bpierre
reviewed
Apr 30, 2024
| const envVars = [ | ||
| `DEPLOYER=${options.deployer}`, | ||
| ]; | ||
| process.env.DEPLOYER = options.deployer; |
This will tell pnpm to use --frozen-lockfile.
danielattilasimon
force-pushed
the
define-ci
branch
2 times, most recently
from
d1048dc
to
7d72198
Compare
It should automatically use --frozen-lockfile when detecting CI, but that doesn't seem to work for some reason.
danielattilasimon
force-pushed
the
define-ci
branch
from
7d72198
to
90d666d
Compare
Hardhat tests were failing when installing dependencies via pnpm v9, why?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This will tell pnpm to use --frozen-lockfile.