-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Editing draft releases often fails #2543
Comments
Hi, thank you for reporting. Which hub version do you use? I cannot reproduce this. |
I'm using the latest version of I do this in three steps.
It's the second and third step that seem to have issues finding the draft release. |
@inktomi I still cannot reproduce; I'm able to attach assets to draft releases just fine. Can you debug by setting |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
We are running into the same issue, I enabled logging, and here is the result: Logs
|
I looks like the tag doesn't exist. However, the tag is created upfront and starts the build. The step before this one is the creation of the release from the existing tag. Using |
Is it possible that this is caused by #2920? The current behavior for finding a specific release is to search through all releases (in pages of 100) to find the one with the matching tag name. I've got a PR up (#3321) to change that to start using the endpoint for actually fetching a single release by tag name, which should alleviate a lot of these types of issue. |
|
Command attempted:
hub release edit v-1.2.3-0 --attach test.png -m ""
What happened:
Unable to find release with tag name `v-1.2.3-0'
More info:
hub release --include-drafts show v-1.2.3-0
This shows that the release is an untagged release. I created it via
hub release create --draft --message="Test" v-1.2.3-0
The text was updated successfully, but these errors were encountered: