-
-
Notifications
You must be signed in to change notification settings - Fork 95
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
Notice: PGP key changed / Release automation #173
Comments
This does produce a bit-by-bit compatible tarball for me, I'm using this command in many projects 😉
You are free to create your own tarball, just sharing in case you are curious 🙂 |
https://github.com/Cloudef/bemenu/blob/master/GNUmakefile#L151 Tried it, sadly doesn't seem to work either |
Why have both |
@Earnestly it's to make sure the tag matches VERSION. I did mistake last time by not bumping VERSION file. Releases are automatically generated on tag pushes. #130 |
This should be covered by the |
That's true. I guess my brain semantically mapped the GIT_TAG variable as a better candidate as a argument for git archive for a "git tag" :) Though it doesn't matter as both of them should be same the time the test passes. |
The PGP key used now is 29317348D687B86B, I've signed this with the old key. The key can also be found from my website https://cloudef.pw/bemenu-pgp.txt
Also since the
git archive
doesn't seem to produce bit-by-bit compatible tarball to github generated one, the releases now include a tarball generated by the CI, thus if you want to verify the source tarball, do not download the github generated one. Instead get thebemenu-<version>.tar.gz
andbemenu->version>.tar.gz.asc
files.The text was updated successfully, but these errors were encountered: