api.github.com/repos/ORG/REPO/releases #181151
Replies: 2 comments
-
|
💬 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.
-
|
Here is a video walkthrough that illustrates the bug. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Bug
Body
Hello,
Until recently I was able to use the api to one-shot a release creation using the
releasesendpoint. This has begun failing recently causing some CI failures that were based on verifying functionality that wraps the github api. In short the following:Will result in the creation of an ostensible tag listed under the tag tab (
https://github.com/<ORG>/<REPO>/tags) when viewed in the GitHub UI, but when I select theReleaseName"tag" it presents as a release.My api wrapper relies on release creation being atomic functionality. This looks like a bug as a POST to the releases endpoint should create a release.
Beta Was this translation helpful? Give feedback.
All reactions