I have released a Release v1.0.0 on github. And got its DOI in Zenodo. But now I have added some scripts and released v1.0.1. But when I check it in Zenodo, it still shows v1.0.0. How can I update this version and get DOI?
The repository is https://github.com/Yujie-Cui/WB-channels
In addition, when I click upload at the front of the page, it shows
The public here shows 0. But the draft shows 1. The draft shows what I posted. But I have obtained the earliest version of DOI.
Thanks!
The documentation on the Zenodo homepage doesn't seem to explain this explicitly but the documentation on Github does: Zenodo creates releases from the releases on Github, so to update your entry on Zenodo, you need to create a new release on Github.
Related
I work at a software company which hosts its source code on github. Whenever a new release comes out, the release notes are also generated with it. The release notes are then manually copied by a person and published on slite. Is there any way API or github integration provided by slite, so that when a release note gets published on github, it also gets published on slite without any human involvement?
Is there a way to automatically update the "Releases" version number on a Github page? Either from automatic machinery within Github, or using some API to update it?
(See the release number "3.5.0" in the image below...) Thanks.
This sidebar component shows you the latest release (I believe). If you want to add a release, that can be done using the REST API. You can also update the release using the REST API.
Note that it isn't sufficient to just push a tag here. A release on GitHub is associated with a tag, but it can also have a message and assets (usually binaries or source code) associated with it. You do need such a tag, but you also need to create the actual release on GitHub.
If you want an example of how this can be done with shell scripting, Git LFS has a script that performs this task as part of the release process.
A project I'm involved with wants to do releases only via PyPI and never puts releases in the "Releases" section on their GitHub repo. Is there a way to put a banner or other notice on the /releases page itself , to help point visitors in the right direction and alleviate confusion about the apparent lack of releases of the software? The README file can explain where people should go for releases, but people can still miss the information, especially if they have gotten used to reflexively clicking on the releases link on GitHub repos.
I've read the GitHub documentation about releases but did not find something suitable, nor do I see anything suitable in the repository settings section.
A workaround would be to put a "shifting tag" (meaning, a tag regularly put on the latest master HEAD) called:
See_README_releases_only_on_PyPi
That way, the empty Release page would at least displays tags, starting with that most recent one.
According to Github docs, the last release of a project is supposed to be automatically marked as "latest release", visually and with "/releases/latest" url suffix.
https://help.github.com/articles/linking-to-releases/#linking-to-the-latest-release
Here is one example where it works.
https://github.com/d3/d3-scale/releases
https://github.com/d3/d3-scale/releases/latest
But it doesn't work in the following project. The last release is not visually marked as "latest", and the "/releases/latest" suffix doesn't work.
https://github.com/ramtob/d3-parallel-links/releases
https://github.com/ramtob/d3-parallel-links/releases/latest
Why doesn't it work here? What is missing?
To setup a release, just go to : https://github.com/username/project/releases/new
You'll find the explications you need. To answer to your question properly, here is the "why" you don't have any release yet (quote from github).
There aren’t any releases here
Releases are powered by tagging specific points of history in a repository. They’re great for marking release points like v1.0.
A release is a tagged version of your app on the branch master.
I've found out that in github you can use a Latest Release button or link to always clone the latest tag from that project without specifically specifying the version number, however if I use something like this: (links are just examples project is private)
https://github.com/company/project1/releases/latest (this is how I've learned the latest release link should be accessed)
it just redirects me back to:
https://github.com/company/project1/releases/
My guess is that I have to enable the Latest Release button/tag somehow? How will I do it?
It works only if your release has an artificat associated to it.
See for instance: https://github.com/reactiveui/ReactiveUI/releases/latest
If you define releases without ever attaching a binary to any of them, then 'latest' redirects you to the releases page of your project indeed.