[26.x] archive 26.1 release notes + backports #29899

1. 
   glozow commented at 12:31 pm on April 17, 2024: member

   Archives 26.1 release notes and adds draft release notes for 26.2rc1

   Also backports:

   • #29691
   • #29869
   • #28554
   • #29747
   • #29853
   • #29856
   • #29764
   • #29776
   • #29985
   • #30094
   • #29870
   • #30149
   • #30085
2. [doc] archive 26.1 release notes c21bbcc898
3. Change Luke Dashjr seed to dashjr-list-of-p2p-nodes.us

   To avoid issues with DNS blacklisting, I've setup a separate domain for my DNS seed.
   
   Github-Pull: #29691
   Rebased-From: 4f273ab4360c9aa72c2feb78787e1811ab58dc16

   d39ea519c7
4. [rpc, bugfix] Enforce maximum value for setmocktime

   Github-Pull: #29869
   Rebased-From: c2e0489b7125cceaeef355fc274dd8988822fff4

   a81a9228fb
5. glozow added the label Backport on Apr 17, 2024
6. 
   DrahtBot commented at 12:31 pm on April 17, 2024: contributor

   The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

   Code Coverage

   For detailed information about the code coverage, see the test coverage report.

   Reviews

   See the guideline for information on the review process.

   Type	Reviewers
   ACK	stickies-v, willcl-ark

   If your review is incorrectly listed, please react with 👎 to this comment and the bot will ignore it on the next update.

7. Throw error if invalid parameters passed to getnetworkhashps RPC endpoint

   Github-Pull: #28554
   Rebased-From: 9ac114e5cd9d8ade3a1d9f3d76a08ff59a3f1658

   bf5b6fc8a7
8. DrahtBot added the label CI failed on Apr 17, 2024
9. DrahtBot removed the label CI failed on Apr 17, 2024
10. bitcoin deleted a comment on Apr 17, 2024
11. dasibcryptoidology approved
12. glozow force-pushed on Apr 29, 2024
13. glozow force-pushed on Apr 29, 2024
14. glozow force-pushed on Apr 29, 2024
15. DrahtBot added the label CI failed on Apr 29, 2024
16. glozow force-pushed on May 13, 2024
17. DrahtBot removed the label CI failed on May 13, 2024
18. glozow force-pushed on May 14, 2024
19. glozow marked this as ready for review on May 14, 2024
20. 
    jonatack commented at 2:15 pm on May 16, 2024: contributor

    Propose the first commit of #30085 for backport.
21. glozow force-pushed on May 23, 2024
22. glozow force-pushed on May 23, 2024
23. in doc/release-notes.md:105 in a29e9e5fea outdated

    123-- Roman Zeyde
    124-- stickies-v
    125-- UdjinM6
    126-
    127-As well as to everyone that helped with translations on
    128-[Transifex](https://www.transifex.com/bitcoin/bitcoin/).
    

    ---

    ---

    

    stickies-v commented at 3:44 pm on May 23, 2024:

    I think we usually keep this in for backports too?
24. stickies-v approved
25. 
    stickies-v commented at 4:00 pm on May 23, 2024: contributor

    ACK a29e9e5fea98925cd19c4e9e8738de67d04da549 modulo release notes touchup

    All backport commits are clean, except for:

    • b1481467bdf6c1300341d1e2ca399ca5e30fdace: because of #28955
    • 109b9d74f50651aa4765d6eec047f09e497215fd: because of LLVM version bump in #29659
    • 7d13e6ab51a02db33fea4df61f70c3f919016a8b: because of removing -rpcserialversion (#28890, and #28438)

    All of these look good to me.

    nit: in b1481467bdf6c1300341d1e2ca399ca5e30fdace commit message, it should be Github-Pull: [#29776](/bitcoin-bitcoin/29776/) instead of Github-Pull: [#29767](/bitcoin-bitcoin/29767/)

26. Fix #29767, set m_synced = true after Commit()

    Github-Pull: #29776
    Rebased-From: bbe82c116e72ca0638751e063bf564cd1fe5c4d5

    bb46b90b2e
27. depends: fix mingw-w64 Qt DEBUG=1 build

    The issue is that compilation is done with `x86_64-w64-mingw32-g++-posix`,
    but then linking is done with `x86_64-w64-mingw32-g++`.
    
    I'm guessing this has been broken since #24131
    (01d1845a80ae48d741deea695ddce95d940ab0d8), but have not checked.
    
    Fixes #29734.
    Unblocks #29527 (now DEBUG=1 builds can be tested).
    
    Github-Pull: #29747
    Rebased-From: b7e7e727abd86104ee58beb648a94e2f453d1f6d

    e4859c82c7
28. sign: don't assume we are parsing a sane Miniscript

    The script provided for signature might be externally provided, for
    instance by way of 'finalizepsbt'. Therefore the script might be
    ill-crafted, so don't assume pubkeys are always 32 bytes.
    
    Thanks to Niklas for finding this.
    
    Github-Pull: #29853
    Rebased-From: 4d8d21320eba54571ff63931509cd515c3e20339

    d9ef6cf934
29. ci: Bump s390x to ubuntu:24.04

    Re-enable feature_init
    
    Github-Pull: #29856
    Rebased-From: fadf7e90dc10e212e59bb294209bab2e73c47800

    7ecdb0846d
30. doc: Suggest installing dev packages for debian/ubuntu qt5 build

    Pretty much all library packages were renamed in the 64-bit time_t
    migration to add `t64` (even on 64-bit platforms).
    
    Instead of complicating the doc with conditional package names, suggest
    installing the `-dev` packages which still have the same name, and
    besides that, are the right way to go about it as they contain the
    "user facing" C++ headers needed to build against Qt5.
    
    For Fedora, devel packages are already suggested.
    
    This affects Ubuntu 24.04 and Debian Testing.
    
    Github-Pull: #29764
    Rebased-From: a3c6a13cb23999fa70c428f1229acbf1b3883f11

    c587753f48
31. ci: Pull in qtbase5-dev instead of seperate low-level libraries

    Fix CI build for t64 migration.
    
    Github-Pull: #29764
    Rebased-From: 6c2990416e2dabd845f5ec50ec6ff138136c9b08

    f9b76bae57
32. depends: Fix build of Qt for 32-bit platforms

    The 32 to 64-bit time_t transition causes a build failure in the built-in
    zlib about conflicting _TIME_BITS and _FILE_OFFSET_BITS.
    
    Note that zlib doesn't use time_t at all, so it is a false alarm.
    
    Take the following patch from upstream zlib:
    https://github.com/madler/zlib/commit/a566e156b3fa07b566ddbf6801b517a9dba04fa3.patch
    
    Closes #29980.
    
    Github-Pull: #29985
    Rebased-From: 2e266f33b5d2be5c233c2c692481f75785714fa1

    7f45e00174
33. rpc: move UniValue in blockToJSON

    Without explicitly declaring the move, these UniValues get copied,
    causing increased memory usage. Fix this by explicitly moving the
    UniValue objects.
    
    Used by `rest_block` and `getblock` RPC.
    
    Github-Pull: #30094
    Rebased-From: b77bad309e92f176f340598eec056eb7bff86f5f

    6685affe92
34. rpc: Reword SighashFromStr error message

    Github-Pull: #29870
    Rebased-From: fa6ab0d020d0b1492203f7eb2ccb8051812de086

    96d0e818c5
35. windeploy: Renew certificate

    Github-Pull: #30149
    Rebased-From: 9f4ff1e9659597307f62510f1885ad8da3a1d9a3

    ec5ce2fb2b
36. p2p, bugfix: detect addnode cjdns peers in GetAddedNodeInfo()

    Addnode (manual) peers connected to us via the cjdns network are currently not
    detected by CConnman::GetAddedNodeInfo(), i.e. fConnected is always false.
    
    This causes the following issues:
    
    - RPC `getaddednodeinfo` incorrectly shows them as not connected
    
    - CConnman::ThreadOpenAddedConnections() continually retries to connect them
    
    Github-Pull: #30085
    Rebased-From: 684da9707040ce25d95b2954eda50b811136d92c

    21d9aaae32
37. [doc] add draft release notes for 26.2rc1 aa7e876953
38. glozow force-pushed on May 23, 2024
39. 
    glozow commented at 4:07 pm on May 23, 2024: member

    Thanks so much @stickies-v! Nice catch, fixed the transifex line and PR number
40. 
    stickies-v commented at 4:10 pm on May 23, 2024: contributor

    re-ACK aa7e876953c460e8ff97a719fdb18f4f3ac4896f, only changes are fixing commit msg and transifex reference
41. willcl-ark approved
42. 
    willcl-ark commented at 8:02 am on May 24, 2024: member

    ACK aa7e876953c460e8ff97a719fdb18f4f3ac4896f

    Checked that all backports were applied without modifcation where possible

43. glozow merged this on May 24, 2024
44. glozow closed this on May 24, 2024

    ---

Contributors
glozow DrahtBot dasibcryptoidology jonatack stickies-v willcl-ark

Labels
Backport