You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So they're not quite in sync here, and if one uses a git clone, for example, one would get the version as 1.5.1.dev0 and so on. So, could the info.json file also be updated in the repo when a new release is tagged please so that the release and tagged tar are identical?
The text was updated successfully, but these errors were encountered:
Hi. Thanks for the report. It seems there was a mistake in the latest release and the tagged commit didn't contain the usual info updating. We'll make sure to fix it and push out a new release soon. Sorry for the trouble.
I'll keep this issue open until the new release is out.
While updating the Fedora package, I noticed that the automatically generated release tar here on GitHub still says "dev" in the info.json file:
https://github.com/G-Node/nixpy/archive/refs/tags/1.5.1.tar.gz
because the info.json file at that tag/commit still says so:
nixpy/nixio/info.json
Line 2 in b140b78
However, if one uses the released tar (manually generated?), it says "release":
https://github.com/G-Node/nixpy/releases/download/1.5.1/nixio-1.5.1.tar.gz
So they're not quite in sync here, and if one uses a git clone, for example, one would get the version as 1.5.1.dev0 and so on. So, could the info.json file also be updated in the repo when a new release is tagged please so that the release and tagged tar are identical?
The text was updated successfully, but these errors were encountered: