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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is the
s
in the version intentional or a mistype?Also, if we're updating the pnpm version in our Dockerfiles, then we also need to update the pnpm versions specified here, otherwise unit tests won't pass
https://github.com/electron-userland/electron-builder/blob/master/package.json#L78
https://github.com/electron-userland/electron-builder/blob/master/.github/actions/pretest/action.yml#L13
https://github.com/electron-userland/electron-builder/blob/master/.github/actions/pnpm/action.yml#L7
With the updated pnpm version, I think the lockfile needs to be updated as well via
pnpm i
? :)Alternatively, you could just update the
ARG NODE_VERSION
in this PR and not the pnpm version and I could take care of the rest