release-process: Add signing of tarball plus minor improvements #1709

1. 
   real-or-random commented at 10:02 AM on July 22, 2025: contributor

   No description provided.

2. release-process: Refactor 9b793ce593
3. release-process: Add signing of tarball

   Resolves #1175.

   ba25edbbe6
4. release-process: Fix nits 8f9530357b
5. release-process: Add "cleaning up" e6aa166c08
6. real-or-random added the label meta/development on Jul 22, 2025
7. real-or-random added the label release on Jul 22, 2025
8. 
   fanquake commented at 9:45 AM on July 24, 2025: member

   You might be interested in this downstream discussion: https://github.com/gentoo/gentoo/pull/43104#discussion_r2224178492.

9. real-or-random added this to the milestone 0.7.1 on Sep 16, 2025
10. 
    hebasto commented at 3:16 PM on September 22, 2025: member

    Would you mind also considering this comment?

11. 
    real-or-random commented at 8:22 PM on September 25, 2025: contributor

    We should look into the https://github.com/bitcoin-core/bitcoin-maintainer-tools/blob/main/make-tag.py script. Not sure if it's immediately compatible with libsecp256k1 as it performs a few checks probably specific to Core but the idea to include a Treehash512 in the tag description is clever.

12. 
    fanquake commented at 12:26 PM on January 30, 2026: member

    Push the milestone here (and on #1175)?

13. real-or-random removed this from the milestone 0.7.1 on Jan 30, 2026
14. real-or-random added this to the milestone 0.7.2 on Jan 30, 2026
15. 
    theStack commented at 8:24 PM on July 7, 2026: contributor

    Concept ACK

    We should look into the https://github.com/bitcoin-core/bitcoin-maintainer-tools/blob/main/make-tag.py script. Not sure if it's immediately compatible with libsecp256k1 as it performs a few checks probably specific to Core but the idea to include a Treehash512 in the tag description is clever.

    Took a stab at that, adapting the script to the versioning scheme that libsecp256k1 uses (i.e. fixed major.minor.patch without rcs): https://github.com/theStack/secp256k1/commits/make-tag-py_libsecp_edition/tools/make-tag.py A quick test based on an extra commit that sets a fake version 0.23.42 and switches IS_RELEASE to true was successful:

    <details> <summary>make-tag.py libsecp edition experiments</summary>

    $ ./tools/make-tag.py v0.23.42
    libsecp256k1 0.23.42
    
    Tree-SHA512: 4767cfb6d17034f166f3c3ab261c7434dbe610ffd9e0117cdc797f5bd24e2fb9dbb6a55a571c6874a23800589014de8c1d928e7c272309fa65be4985c5602abe
    
    $ git show v0.23.42
    tag v0.23.42
    Tagger: Sebastian Falbesoner <sebastian.falbesoner@gmail.com>
    Date:   Tue Jul 7 22:14:14 2026 +0200
    
    libsecp256k1 0.23.42
    
    Tree-SHA512: 4767cfb6d17034f166f3c3ab261c7434dbe610ffd9e0117cdc797f5bd24e2fb9dbb6a55a571c6874a23800589014de8c1d928e7c272309fa65be4985c5602abe
    -----BEGIN PGP SIGNATURE-----
    ...
    -----END PGP SIGNATURE-----
    
    $ ./tools/treehash512.py 
    4767cfb6d17034f166f3c3ab261c7434dbe610ffd9e0117cdc797f5bd24e2fb9dbb6a55a571c6874a23800589014de8c1d928e7c272309fa65be4985c5602abe
    

    </details>

Contributors

real-or-randomfanquakehebastotheStack

Milestone
0.7.2