Added debug output to see:
- Git URL rewrites configuration
- Environment variables
- Verbose yarn install output
This will help identify why yarn install is failing after the GITHUB_TOKEN fix.
https://claude.ai/code/session_015R3U3kiprQiNTTNNt31Sg6
Fixed 4 failing workflow checks:
1. **Build/Lint/Test workflows**: Fixed yarn install authentication
- Changed Git URL rewrite to include GITHUB_TOKEN in all rewrites
- Added GITHUB_TOKEN and GIT_TERMINAL_PROMPT env vars to yarn install step
- Now correctly handles github: dependencies (like libsignal)
2. **PR Comment workflow**: Fixed missing token error
- Changed from secrets.PERSONAL_TOKEN to secrets.GITHUB_TOKEN
- Workflow now has proper authentication
Root cause: Yarn 4.x was trying to clone github: dependencies via SSH,
but CI had no SSH keys. Git config now rewrites ALL GitHub URLs to
HTTPS with token authentication.
https://claude.ai/code/session_015R3U3kiprQiNTTNNt31Sg6
- Fixed cache paths for Yarn 4 (node_modules + .yarn/install-state.gz)
- Updated all workflows to use actions/cache@v4
- Added auto-merge for WhatsApp version update PRs
https://claude.ai/code/session_01QPt4WssG6jjEciQKdVpFtK
Fixes "Permission denied (publickey)" error when Yarn tries to fetch
libsignal dependency via SSH in GitHub Actions.
Added git config to force HTTPS instead of SSH for all GitHub URLs
in all workflows that run yarn install.
https://claude.ai/code/session_01QPt4WssG6jjEciQKdVpFtK
Claude