Checklist
What happened?
I noticed when trying to test our new release actions using conda-pypi that the update repository workflow was failing with:
Run FORK="$(gh repo fork --clone=false --default-branch-only 2>&1 | awk '{print $1}' | sed 's|^https://github.com/||')"
Error: Unable to process file command 'env' successfully.
Error: Invalid format 'Try'
A representative workflow run is here: https://github.com/conda/conda-pypi/actions/runs/33553637478/job/100009043869
In #1441, I changed the logic to use the gh API to try to get better error messages, now we are getting:
Run FORK="$(gh api repos/{owner}/{repo}/forks --method POST -f default_branch_only=true --jq .full_name)"
gh: Bad credentials (HTTP 401)
Error: Process completed with exit code 1.
A representative workflow from that is here (run from a branch): https://github.com/conda/conda-pypi/actions/runs/33688901290/job/100442825039.
I checked the gh CLI changelog and there was no significant changes that would impact this. I haven't been able to determine root cause yet, but I think as a next step we should try rotating our SYNC_TOKEN.
Additional Context
No response
Checklist
What happened?
I noticed when trying to test our new release actions using conda-pypi that the update repository workflow was failing with:
A representative workflow run is here: https://github.com/conda/conda-pypi/actions/runs/33553637478/job/100009043869
In #1441, I changed the logic to use the gh API to try to get better error messages, now we are getting:
A representative workflow from that is here (run from a branch): https://github.com/conda/conda-pypi/actions/runs/33688901290/job/100442825039.
I checked the gh CLI changelog and there was no significant changes that would impact this. I haven't been able to determine root cause yet, but I think as a next step we should try rotating our SYNC_TOKEN.
Additional Context
No response