Skip to content

Commit

Permalink
chore: pin global turbo to 1.x release (#8196)
Browse files Browse the repository at this point in the history
### Description

Just so we don't accidentally break all of our workflows when we cut a
2.0 canary we should pin ourselves to the latest 1.x release.

Once a 2.0 canary is released we will migrate ourselves and unpin the
version.

### Testing Instructions

CI
  • Loading branch information
chris-olszewski committed May 22, 2024
1 parent 5e3bc0b commit e184969
Showing 1 changed file with 2 additions and 1 deletion.
3 changes: 2 additions & 1 deletion .github/actions/install-global-turbo/action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,8 @@ runs:
steps:
- name: Install Turbo globally
shell: bash
# Until we are migrate ourselves to 2.0 we pin to the latest 1.x release
run: |
VERSION=$(npm view turbo --json | jq -r '.versions | last')
echo "Latest published version: $VERSION"
npm i -g turbo@$VERSION
npm i -g turbo@1.13.4-canary.5

0 comments on commit e184969

Please sign in to comment.