Bug Report: Publishing a release via GitHub actions fails for repos created on 2025-11-25 #180369
-
Select Topic AreaBug BodyWhen trying to create a release from a GitHub action job via a step like this: steps:
- name: test release
env:
GH_REPO: ${{ github.repository }}
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
run: gh release create test --title test --notes testIt fails for repos newly created today, while the very same action works as expected on pre-existing repos created in the past. Despite the permissions of the Example:
Looking through the repo settings of both I cannot spot any differences in permissions or similar. Performing the release creation manually via PAT or the UI works as expected for both types of repos, only publishing a release with the |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments · 8 replies
-
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
Beta Was this translation helpful? Give feedback.
-
|
This is a duplicate of this discussion It first came up as an issue within the GITHUB_TOKEN in actions, but also appears to not work in the cli. |
Beta Was this translation helpful? Give feedback.
-
|
This also affected an old repo of mine where I was trying to add CI/CD for the first time. |
Beta Was this translation helpful? Give feedback.
-
|
Hey Friend 👋 What’s Going On?
✅ How to Fix It?
If you do that, the gh release create ... command in your action should be able to push the release without the 422 error. |
Beta Was this translation helpful? Give feedback.
-
|
My just created repository already has 'Read and write' permissions under settings -> Actions -> General, but I still cannot run the 'gh release create', even though I am using a workflow that has worked flawlessly in other repositories up until yesterday. |
Beta Was this translation helpful? Give feedback.
-
|
Same as @xworld21, fresh repo created today, This needs to be fixed on GitHub side, gladly ChatGPT was able to find this report, I was losing my mind comparing settings and pipelines between repos that I know have working releases and new repo. 
|
Beta Was this translation helpful? Give feedback.
-
|
Same issue here. New repo. 😞 |
Beta Was this translation helpful? Give feedback.
-
|
same issue as well on a repo created today. I set write permissions on the GitHub settings page and added "permissions: contents: write" in the yaml config |
Beta Was this translation helpful? Give feedback.
-
|
same problem. It works in another repo, but fails in the older one. The same workflow code, same repo permissions, no secrets/variables/tokens. Copilot couldn't solve it. The only finding we made: full results: https://github.com/Roman86/react-combo-provider/actions/runs/19688167297/workflow What's interesting that another workflow (different github action) succeeded in the same repo: UPDATE: the service is fixed the next day |
Beta Was this translation helpful? Give feedback.
-
|
The issue is now fixed. |
Beta Was this translation helpful? Give feedback.
-
|
I'm confirming. Re-running the same failed job works just fine now |
Beta Was this translation helpful? Give feedback.
-
|
yep, can confirm everything works as expected again 🎉 |
Beta Was this translation helpful? Give feedback.
The issue is now fixed.