Skip to content

Commit

Permalink
chore: bump pnpm action version (#8676)
Browse files Browse the repository at this point in the history
### Description

Our release was broken due to a bump in the global NodeJS version which
causes a failure when trying to setup `pnpm`:
https://github.com/vercel/turbo/actions/runs/9812173678

Following directions on pnpm/action-setup#135
to update to v4 of the action

We also need to add `ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION` in order
to keep using Node 16 for checking out our code for our MUSL builds
where we need an old version of GLIBC.

### Testing Instructions

Test run: https://github.com/vercel/turbo/actions/runs/9812969175
  • Loading branch information
chris-olszewski authored Jul 5, 2024
1 parent 0783973 commit 7d30f41
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 1 deletion.
2 changes: 1 addition & 1 deletion .github/actions/setup-node/action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ runs:
using: "composite"
steps:
- name: Setup pnpm
uses: pnpm/action-setup@v2.2.4
uses: pnpm/action-setup@v4

- name: Setup Node.js
uses: actions/setup-node@v3.6.0
Expand Down
3 changes: 3 additions & 0 deletions .github/workflows/turborepo-release.yml
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,9 @@ env:
CARGO_PROFILE_RELEASE_LTO: true
NPM_TOKEN: ${{ secrets.NPM_TOKEN }}
RELEASE_TURBO_CLI: true # TODO: do we need this?
# Needed since we need to build on Xenial which doesn't have a new enough
# GLIBC to use Node 20.
ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION: true

on:
workflow_dispatch:
Expand Down

0 comments on commit 7d30f41

Please sign in to comment.