release: Prepare for 0.7.0 #1707

pull real-or-random wants to merge 2 commits into bitcoin-core:master from real-or-random:202507-v0.7.0 changing 5 files +15 −14
  1. real-or-random commented at 2:23 PM on July 21, 2025: contributor

    No description provided.

  2. real-or-random added the label release on Jul 21, 2025
  3. real-or-random force-pushed on Jul 21, 2025
  4. real-or-random commented at 2:28 PM on July 21, 2025: contributor

    I plan to create a signed tarball using this code and attach it to the github release. We could add the code the release process afterward if we're happy with the result:

    git archive --output "libsecp256k1-0.7.0.tar.gz" --prefix "libsecp256k1-0.7.0/" v0.7.0
gpg --local-user "09E03F871092E40E106E902B33BC86AB80FF5516" --detach-sign "libsecp256k1-0.7.0.tar.gz"
gpg --verify "libsecp256k1-0.7.0.tar.gz.sig"

    edit: Some alternatives that were rejected after discussing with @jonasnick:

    • We considered *.zip for compatibility with Windows, but it turns out that Windows 10/11 has a built-in tar command that can handle .tar.gz, so let's prefer the latter.
    • We considered creating a SHA256SUMS.txt as common for some projects, but it's just pointless overhead when signing a single file.
  5. jonasnick commented at 2:30 PM on July 21, 2025: contributor

    utACK 8ee77ba7364a3d69952a291ac25d8675b45b43f9

  6. real-or-random force-pushed on Jul 21, 2025
  7. real-or-random commented at 2:36 PM on July 21, 2025: contributor

    Force-pushed to prepend a commit that hopefully fixes CI

  8. real-or-random force-pushed on Jul 21, 2025
  9. sipa commented at 2:56 PM on July 21, 2025: contributor

    utACK 5b0500ea3f041b65ede661d85d67dae01abcee5b

  10. in .github/workflows/ci.yml:659 in 5b0500ea3f outdated 
     651 | @@ -652,10 +652,11 @@ jobs:
 652 |  
 653 |        - name: Symbol check
 654 |          if: ${{ matrix.configuration.symbol_check }}
 655 | +        shell: bash
 656 |          run: |
 657 |            py -3 --version
 658 |            py -3 -m pip install lief
 659 | -          py -3 .\tools\symbol-check.py build\bin\RelWithDebInfo\libsecp256k1-5.dll
 660 | +          py -3 ./tools/symbol-check.py build/bin/RelWithDebInfo/libsecp256k1-*.dll
    fanquake commented at 2:57 PM on July 21, 2025:

    Looks like there's another instance of this to change in ci/ci.sh?

    real-or-random commented at 3:12 PM on July 21, 2025:

    sigh yes

    real-or-random commented at 3:22 PM on July 21, 2025:

    fixed

  11. ci: Don't hardcode ABI version f67b0ac1a0
  12. release: Prepare for 0.7.0 a3e742d947
  13. real-or-random force-pushed on Jul 21, 2025
  14. real-or-random added the label ci on Jul 21, 2025
  15. sipa commented at 4:18 PM on July 21, 2025: contributor

    utACK a3e742d9478c202cbe93e721567e0f1dea1c8bde

  16. jonasnick approved
  17. jonasnick commented at 4:35 PM on July 21, 2025: contributor

    utACK a3e742d9478c202cbe93e721567e0f1dea1c8bde

  18. jonasnick commented at 5:52 PM on July 21, 2025: contributor

    tACK a3e742d9478c202cbe93e721567e0f1dea1c8bde

  19. real-or-random merged this on Jul 21, 2025
  20. real-or-random closed this on Jul 21, 2025
  21. real-or-random referenced this in commit b9313c6e1a on Jul 21, 2025
  22. fanquake referenced this in commit 5600e6fc4b on Jul 22, 2025
  23. fjahr referenced this in commit b6fc8c52d5 on Jul 24, 2025
  24. in configure.ac:18 in a3e742d947 
      18 |  # interface and therefore only increase the revision.
  19 | -define(_LIB_VERSION_CURRENT, 5)
  20 | -define(_LIB_VERSION_REVISION, 1)
  21 | +define(_LIB_VERSION_CURRENT, 6)
  22 | +define(_LIB_VERSION_REVISION, 0)
  23 |  define(_LIB_VERSION_AGE, 0)
    hebasto commented at 1:48 PM on July 27, 2025:

    To make it easier to verify versioning changes, I suggest including the output of the ./tools/check-abi.sh tool in the PR description in the future.

    For example, for this one: <img width="938" height="783" alt="image" src="https://github.com/user-attachments/assets/36df78cc-a60c-412d-bcb4-451285be071b" />

  25. hebasto commented at 1:48 PM on July 27, 2025: member

    Post-merge ACK a3e742d9478c202cbe93e721567e0f1dea1c8bde.

  26. saikiran57 referenced this in commit abe11bd67c on Jul 28, 2025
  27. macgyver13 referenced this in commit ef5eeb6c13 on Aug 13, 2025
  28. janus referenced this in commit e0ffd31e87 on Sep 14, 2025
  29. vmta referenced this in commit 2b25f561a0 on Sep 21, 2025
  30. real-or-random referenced this in commit a3733f33c1 on Feb 25, 2026
  31. github-actions[bot] referenced this in commit 758d4e90b4 on Mar 1, 2026
  32. github-actions[bot] referenced this in commit 68a2178f22 on Mar 1, 2026
  33. github-actions[bot] referenced this in commit a8bc1a0b2b on Mar 1, 2026
  34. 0x000000000019d6689c085ae165831e934ff76 referenced this in commit 3b9450150d on Mar 2, 2026
  35. csjones referenced this in commit a4d92824ae on Mar 2, 2026
Contributors
real-or-randomjonasnicksipafanquakehebasto
Labels
cirelease
Linked (view graph)
#1708 release cleanup: bump version after 0.7.0
github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin-core/secp256k1. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-05-19 06:52 UTC