-
Notifications
You must be signed in to change notification settings - Fork 239
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
Github release failed #1181
Comments
I'm experiencing the same issue (which also seems to be a related to #799) |
I experienced the same issue today - in #1214 I suggested the following workaround (that worked for me) from #1214 Thus adding event ids would at leas allow to pinpoint the origin of these bugs. |
I've also just experienced the same issue. |
my two cents: I was struggling with this, then found this other issue #799 That worked for some of my repos, but not for others. Here are the things I tried:
These steps fixed all but one of my repos. For the final one, I removed all but the master branch, and then it worked. I'm not sure which of the steps I did are strictly necessary, so use your best judgment and good luck. |
I am getting the same error msg for my two newly released (first time) repos :( Any help will be appreciated. |
could you please post links to repos so I can have a look? |
Not at all sure what the problem is, but could you try to do this:
If that doesn't work, I don't know what does, so fingers crossed. |
Ok so I tried as you suggested. Did a small edit to readme to generate new SHA and created new release as 1.0.2 and it worked for one of the repo. :) |
I'm also having this problem on this repo: https://zenodo.org/account/settings/github/repository/epiasini/SubPID I've already tried doing as @jspaaks suggested above (minor change, new commit, new tag with "pure" semantic versioning-style tag 0.2.1), but no luck :( . Any idea? Thanks! |
Hey Epiasini, |
That worked! I guess the key step I was missing was that I had to turn the integration off and on again (besides dropping the "v" in my tag names). Thanks a lot @asingh33 ! |
I've followed all the suggestions above but am still receiving a "failed" error message |
Hi @ms609, |
Ah, I missed that titles needed to follow semantic versioning too. I've renamed, so will see whether this helps on the next release. (It turns out that it's not too difficult to update manually, which is what I have done for the time being.) Thanks for the suggestion. |
I can confirm that in my case, the issue was an unrecognized license. Per #1448, The |
An even more complete place to find the valid license IDs is our REST API endpoint. We now have official documentation for it. This of course doesn't cancel the fact that we should provide a more helpful UX as discussed in #1606 |
For those looking for information on where to find errors on GitHub and Zenodo, I included some text in our best practices guide here: https://guide.esciencecenter.nl/citable_software/making_software_citable.html Hope that proves helpful to someone. Just in case the document gets moved or removed, find the permalink here |
I hope this get's open again. I had the following error on my previous release and my new release was not even captured by zenodo....
I have no idea what to do about it, since the error message does not say anything useful and I don't know where to search for more info... The issues are happening with the following repository: https://github.com/Socrats/EGTTools for releases 0.1.8 and 0.1.9 |
@Socrats: I suspect the escape in your name in CITATION.cff, at least cffconvert --url https://raw.githubusercontent.com/Socrats/EGTTools/master/CITATION.cff --validate Maybe use double escape or no escape. Also, the After making those changes I can release on Zenodo Sandbox (repo with only a copy the CITATION.cff with suggested changes) |
@jspaaks Thanks so much for the help! I have fixed these issues on the CITATION.cff file. I also updated the version to the latest release |
Seemingly only works if I release with tag name without v: This is on Zenodo Sandbox, but should work the same on regular Zenodo Also the repo contents are exactly the same, just a rerelease with different tag and title name. Not sure why it seems to matter. Note the Zenodo Sandbox entries are wiped periodically, it's there for testing only. |
Thanks for the help again. The main issue is that my CI is set to use tags with v to automatically create new releases... I'll have to figure out a different way then.... |
Nice! Yet I still don't get it on zenodo, how can I trigger the publishing of the release manually? |
If you go to https://zenodo.org/account/settings/github/ , do you see your repo listed? |
Of course.
You can retrigger GitHub, but usually this fails, because it will be the same as what's already there. For reference, the retrigger is under your repo's settings, then Webhooks, then tab Recent Deliveries, Click three dots button to expand: Easier way is to bump the patch version in CITATION.cff, this will take care of updating the SHA, then making a new release via the "Draft new release" with the patched version as tag name. (I assume this bypasses your CI, unless said CI triggers based on release_published event) |
This fixed it. Thanks a lot @jspaaks ! |
Woohoo! Glad I could help. |
https://zenodo.org/account/settings/github/repository/pat-s/oddsratio#
Errors
Github payload
The text was updated successfully, but these errors were encountered: