v0.4.1 release aftermath #1468

pull real-or-random wants to merge 5 commits into bitcoin-core:master from real-or-random:202312-release-aftermath changing 2 files +51 −48
  1. real-or-random commented at 4:32 PM on December 21, 2023: contributor

    No description provided.

  2. real-or-random added the label meta/development on Dec 21, 2023
  3. real-or-random added the label release on Dec 21, 2023
  4. release process: Run sanity checks on release PR 429d21dc79
  5. release process: Add email step e7053d065b
  6. real-or-random force-pushed on Dec 21, 2023
  7. real-or-random commented at 4:35 PM on December 21, 2023: contributor

    cc @hebasto

  8. in tools/check-abi.sh:6 in d6274ea331 outdated 
       2 | @@ -3,7 +3,7 @@
   3 |  set -eu
   4 |  
   5 |  default_base_version="$(git describe --match "v*.*.*" --abbrev=0)"
   6 | -default_new_version="master"
   7 | +default_new_version="HEAD"
    hebasto commented at 6:00 PM on December 21, 2023: 
    default_new_version="$(git rev-parse HEAD)"

    Otherwise, the HEAD will be modified, which is not what we want.

    real-or-random commented at 12:00 AM on January 9, 2024:

    I'm not entirely sure what you meant here, but I believe I fixed it

  9. hebasto commented at 6:04 PM on December 21, 2023: member

    Is it a proper moment to unify tag related steps in the "Regular release" and "Maintenance release" sections?

    Regular release: 3. After the PR is merged, tag the commit and push it:

    Maintenance release: 4. After the PRs are merged, update the release branch and tag the commit: 5. Push tag:

  10. jonasnick commented at 2:53 PM on January 3, 2024: contributor

    ACK mod hebasto's comments

  11. release process: Style and formatting nits 9fb7e2f156
  12. check-abi: Default to HEAD for new version ad5f589a94
  13. real-or-random force-pushed on Jan 9, 2024
  14. real-or-random commented at 12:01 AM on January 9, 2024: contributor

    Is it a proper moment to unify tag related steps in the "Regular release" and "Maintenance release" sections?

    Done. Ready for review again.

  15. check-abi: Minor UI improvements b37fdb28ce
  16. real-or-random force-pushed on Jan 9, 2024
  17. hebasto commented at 7:20 PM on January 16, 2024: member

    ACK b37fdb28ce373e359e4d3a9727693b724db31676.

  18. jonasnick approved
  19. jonasnick commented at 7:57 PM on January 16, 2024: contributor

    ACK b37fdb28ce373e359e4d3a9727693b724db31676

  20. jonasnick merged this on Jan 16, 2024
  21. jonasnick closed this on Jan 16, 2024
  22. fjahr referenced this in commit d5f970e647 on Feb 25, 2024
  23. achow101 referenced this in commit b525369f8e on Mar 25, 2024
  24. achow101 referenced this in commit 2189d2f841 on Apr 1, 2024
  25. fanquake referenced this in commit 5354807b00 on Apr 4, 2024
  26. fanquake referenced this in commit 53eec53dca on Apr 4, 2024
  27. hebasto referenced this in commit b6de625950 on May 11, 2024
  28. vmta referenced this in commit 2ef958bb88 on May 20, 2024
  29. janus referenced this in commit 939262869a on Jun 6, 2024
  30. delta1 referenced this in commit 6089844b3c on Apr 2, 2025
  31. div72 referenced this in commit af627d47c3 on Apr 12, 2025
  32. oskarszoon referenced this in commit 0d5c9260f4 on Jul 1, 2025
Contributors
real-or-randomhebastojonasnick
Labels
meta/developmentrelease
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