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

Use latest corepack #2666

Merged
merged 2 commits into from
Feb 3, 2025
Merged

Use latest corepack #2666

merged 2 commits into from
Feb 3, 2025

Conversation

tjmw
Copy link
Member

@tjmw tjmw commented Feb 3, 2025

What does this change?

Uses a more recent version of corepack in CI.

We started seeing issues with pnpm signatures, which is apparently fixed with a later corepack release.

See pnpm/pnpm#9014

How to test

Ensure the build passes.

tjmw added 2 commits February 3, 2025 10:27
We started seeing issues with pnpm signatures, which is apparently fixed
with a later corepack release.

See pnpm/pnpm#9014
@tjmw tjmw marked this pull request as ready for review February 3, 2025 10:37
Copy link
Member

@johnduffell johnduffell left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

looks good, the fact that we do '--global' does that mean it will store it in the GHA cache for next time to improve speed?

@tjmw
Copy link
Member Author

tjmw commented Feb 3, 2025

looks good, the fact that we do '--global' does that mean it will store it in the GHA cache for next time to improve speed?

I'm actually not sure about this. I think I'll merge to unblock things and investigate as a possible follow up optimisation.

@tjmw tjmw merged commit a738d6a into main Feb 3, 2025
48 checks passed
@tjmw tjmw deleted the tw/upgrade-corepack branch February 3, 2025 10:48
@johnduffell
Copy link
Member

looks good, the fact that we do '--global' does that mean it will store it in the GHA cache for next time to improve speed?

I'm actually not sure about this. I think I'll merge to unblock things and investigate as a possible follow up optimisation.

It wasn't necessarily a suggestion, I just wondered why the flag was needed (if at all) given that we get a fresh runner every time.

andrewHEguardian added a commit to guardian/csnx that referenced this pull request Feb 3, 2025
## What are you changing?

- Use a specific version of corepack

## Why?

- The build is failing, see pnpm/pnpm#9014.
This is a proposed fix also used in
guardian/support-service-lambdas#2666
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.

4 participants