Peers disconnect after upgrading to v26.04rc1 #8978
Description
After upgrading to v26.04rc1 all my channels show offline.
In the logs I can see the typical interaction:
2026-03-25T06:43:08.487Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-hsmd: Got WIRE_HSMD_REVOKE_COMMITMENT_TX
2026-03-25T06:43:08.487Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-channeld-chan#3: option_static_remotekey: fields are correct
2026-03-25T06:43:08.487Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-chan#3: channel_gossip: reestablished
2026-03-25T06:43:08.487Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-channeld-chan#3: billboard perm: Reconnected, and reestablished.
2026-03-25T06:43:08.487Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-channeld-chan#3: billboard: Channel ready for use.
2026-03-25T06:43:08.487Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-channeld-chan#3: billboard: Channel ready for use.
2026-03-25T06:43:08.497Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-channeld-chan#3: Trying commit
2026-03-25T06:43:08.497Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-channeld-chan#3: Can't send commit: nothing to send, feechange not wanted ({ SENT_ADD_ACK_REVOCATION:259 }) blockheight not wanted ({ SENT_ADD_ACK_REVOCATION:0 })
2026-03-25T06:43:08.590Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-lightningd: peer_disconnected
2026-03-25T06:43:08.597Z DEBUG 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-connectd: Will try reconnect in 300 seconds
2026-03-25T06:43:08.597Z INFO 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-channeld-chan#3: Peer connection lost
2026-03-25T06:43:08.597Z INFO 035e4ff418fc8b5554c5d9eea66396c227bd429a3251c8cbc711002ba215bfc226-chan#3: Peer transient failure in CHANNELD_NORMAL: channeld: Owning subdaemon channeld died (62208)
It doesn't happen though with a core-lightning peer running v25.12.1.