Repository navigation
v3 doesn't work with SSH deploy key #128
Description
Activity
It's currently used in private repos as a test before general rollout. Works fine there. Could you elaborate on the errors you're seeing? Have you followed the migration guide? https://github.com/getsentry/github-workflows/blob/main/CHANGELOG.md#breaking-changes
Hello 👋
I have similar issues with v3 on the RN repo. I bumped with getsentry/sentry-react-native#5218 following the instructions and I get errors like:25-10-03T14:58:36.6545116Z ##[group]Fetching the repository 2025-10-03T14:58:36.6553858Z [command]/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/heads/antonis/fix-worflows-for-v3:refs/remotes/origin/antonis/fix-worflows-for-v3 2025-10-03T14:58:36.7819362Z ##[error]fatal: could not read Username for 'https://github.com': terminal prompts disabled 2025-10-03T14:58:36.7820425Z The process '/usr/bin/git' failed with exit code 128 2025-10-03T14:58:36.7820801Z Waiting 14 seconds before trying again 2025-10-03T14:58:50.7865683Z [command]/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/heads/antonis/fix-worflows-for-v3:refs/remotes/origin/antonis/fix-worflows-for-v3 2025-10-03T14:58:50.8986324Z ##[error]fatal: could not read Username for 'https://github.com': terminal prompts disabled 2025-10-03T14:58:50.9007818Z The process '/usr/bin/git' failed with exit code 128 2025-10-03T14:58:50.9008395Z Waiting 18 seconds before trying again 2025-10-03T14:59:08.9089471Z [command]/usr/bin/git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules --depth=1 origin +refs/heads/antonis/fix-worflows-for-v3:refs/remotes/origin/antonis/fix-worflows-for-v3 2025-10-03T14:59:09.0209186Z ##[error]fatal: could not read Username for 'https://github.com': terminal prompts disabled 2025-10-03T14:59:09.0257930Z ##[error]The process '/usr/bin/git' failed with exit code 128Thx for the details, I'll check what's going on.
Reacted by Antonis LilisThank you @antonis! I was about to reply here :D
Reacted by Antonis LilisCan you check if CI_DEPLOY_KEY is an environment secret with branch deployment restrictions in the sentry-react-native repository settings (Settings → Secrets and variables → Actions → Environments).
I've just tested danger@v3 on a pet project and works fine vaind/properties.dart#11.
There's a possibility this has something to do with running the updater workflow (that's what fails in the RN PR link) in a PR branch. I'll try something
Reacted by Antonis Lilishmm, v2 ran from the pr just fine: getsentry/sentry-react-native#5252
maybe something with using the action now
No i don't think you've missed anything, likely actions/checkout#664 which indicates the issue is with PAT without expiry date. i'll see if there's a workaround
Reacted by Antonis Lilis- changed the title
[-]Is Danger V3 experimental?[/-][+]v3 doesn't work with PAT without expiration date set[/+]on Oct 9, 2025 - changed the title
[-]v3 doesn't work with PAT without expiration date set[/-][+]v3 doesn't work with SSH deploy key)[/+]on Oct 9, 2025 - changed the title
[-]v3 doesn't work with SSH deploy key)[/-][+]v3 doesn't work with SSH deploy key[/+]on Oct 9, 2025 - added a commit that references this issue
on Oct 9, 2025 - added a commit that references this issue
on Oct 9, 2025
So far I saw 0 repos using V3, I tried locally but I got permission denied errors