Fix Yarn not found in CI by installing it manually in shared workflow #133
Conversation
|
This PR is missing a Jira ticket reference in the title or description. |
|
🥷 Code experts: no user but you matched threshold 10 kb-typeform has most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame: To learn more about /:\ gitStream - Visit our Docs |
1 similar comment
|
🥷 Code experts: no user but you matched threshold 10 kb-typeform has most 👩💻 activity in the files. See details
Activity based on git-commit:
Knowledge based on git-blame: To learn more about /:\ gitStream - Visit our Docs |
This PR updates the Generate persisted operations shared workflow to explicitly install the required Yarn version (1.22.22) via npm instead of relying on asdf and .tool-versions.
🔧 Changes:
• Added npm install -g yarn@1.22.22 after setting up Node.js in the workflow.
🐛 Problem:
Workflows were failing on some repositories with the following error:
This happened because .tool-versions was present in some repos, triggering asdf version management, but the required Yarn version wasn’t installed on the CI runner.
✅ Solution:
Installing Yarn directly with npm ensures the correct version is available regardless of .tool-versions or asdf setup.
This change avoids inconsistent behavior across repositories and ensures the workflow runs reliably everywhere.