-
Notifications
You must be signed in to change notification settings - Fork 23
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
Missing tag for 1.2.0 #24
Comments
done, and I also released an 1.2.1 and pushed the tag and gh release |
Thanks. Could you push the tag for 1.3.0 now? |
Hello! pushed 1.3.0 and 1.4.0 this morning |
The tag for 2.0.1 is also missing. Could you add it? |
Most of the code for 2.0.X is missing. |
There is no code this is just a readme fix |
According to the pyproject file the code is still on 1.4 https://github.com/tardyp/sphinx-jinja/blob/master/pyproject.toml#L3, not 2.0 or 2.0.1 |
you are right I completly forgot to push the code sorry 🙇 |
Thanks! Here is a minor issue: new tags (2.0.0, 2.0.1) are not signed by your GPG key as per https://github.com/tardyp/sphinx-jinja/tags. Could you sign the tags? I'm working on updating the Arch Linux package. In general, we prefer GPG-signed sources and do not remove GPG verification unless there is a good reason. For now, I use GPG-signed tags (https://github.com/archlinux/svntogit-community/blob/packages/python-sphinx-jinja/trunk/PKGBUILD#L17), and GPG-signed tarballs or other signed stuffs are also fine. |
And the 1.2.1 tag is duplicates once with v and without. |
Tag 2.0.2 is still unsigned. @tardyp is there a plan to sign future tags or releases? |
@yan12125 sorryI just signed that tag |
No problem and many thanks! |
Could you please push the tag for 1.2.0 release?
The text was updated successfully, but these errors were encountered: