Versions: update for next version.
What changed, and why it matters
This commit is a routine version-bump housekeeping change. It updates release dates in the pull-request template, shifts the previous/next release version numbers in the Makefile and CI configuration, and replaces one internal test flag with a newer equivalent. There is nothing here that fixes, introduces, or discusses a security issue.
No security action required. Treat as normal repository maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates four non-security files: .github/PULL_REQUEST_TEMPLATE.md (release schedule dates), .github/workflows/ci.yaml (downloaded prior release artifact from v25.12 to v26.04), Makefile (CLN_NEXT_VERSION v26.04→v26.06 and CLN_PREV_VERSION v25.12→v26.04), and tests/test_plugin.py (replaces the test option ‘broken_log’ with ‘i-promise-to-fix-broken-api-user’ for a deprecated-API test). No code behavior affecting network protocol, cryptography, permissions, or asset handling is changed.
Changed components
Release metadata (Makefile, CI workflow, PR template)tests/test_plugin.py (deprecated API test option rename)Inspect captured patch +8 / −8
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index df596985..dac258bf 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,10 +1,10 @@
> [!IMPORTANT]
>
-> 26.04 FREEZE March 11th: Non-bugfix PRs not ready by this date will wait for 26.06.
+> 26.06 FREEZE April 30th: Non-bugfix PRs not ready by this date will wait for 26.09.
>
-> RC1 is scheduled on _March 23rd_
+> RC1 is scheduled on _May 14th_
>
-> The final release is scheduled for April 15th.
+> The final release is scheduled for June 1st.
## Checklist
diff --git a/.github/workflows/ci.yaml b/.github/workflows/ci.yaml
index eefdca61..7ab7618f 100644
--- a/.github/workflows/ci.yaml
+++ b/.github/workflows/ci.yaml
@@ -409,8 +409,8 @@ jobs:
run: |
mkdir old-cln
cd old-cln
- wget https://github.com/ElementsProject/lightning/releases/download/v25.12/clightning-v25.12-ubuntu-24.04-amd64.tar.xz
- tar -xaf clightning-v25.12-ubuntu-24.04-amd64.tar.xz
+ wget https://github.com/ElementsProject/lightning/releases/download/v26.04/clightning-v26.04-ubuntu-24.04-amd64.tar.xz
+ tar -xaf clightning-v26.04-ubuntu-24.04-amd64.tar.xz
- name: Switch network
if: ${{ matrix.TEST_NETWORK == 'liquid-regtest' }}
diff --git a/Makefile b/Makefile
index 682e3f36..223d383e 100644
--- a/Makefile
+++ b/Makefile
@@ -7,10 +7,10 @@ VERSION ?= $(shell git describe --tags --always --dirty=-modded --abbrev=7 2>/de
$(info Building version $(VERSION))
# Next release.
-CLN_NEXT_VERSION := v26.04
+CLN_NEXT_VERSION := v26.06
# Previous release (for downgrade testing)
-CLN_PREV_VERSION := v25.12
+CLN_PREV_VERSION := v26.04
# --quiet / -s means quiet, dammit!
ifeq ($(findstring s,$(word 1, $(MAKEFLAGS))),s)
diff --git a/tests/test_plugin.py b/tests/test_plugin.py
index 3f4f11cb..10b93255 100644
--- a/tests/test_plugin.py
+++ b/tests/test_plugin.py
@@ -4395,7 +4395,7 @@ def test_sql(node_factory, bitcoind):
def test_sql_deprecated(node_factory, bitcoind):
- l1, l2 = node_factory.line_graph(2, opts=[{'allow-deprecated-apis': True, "broken_log": "DEPRECATED API USED: listpeerchannels.max_total_htlc_in_msat"}, {}])
+ l1, l2 = node_factory.line_graph(2, opts=[{'i-promise-to-fix-broken-api-user': 'listpeerchannels.max_total_htlc_in_msat'}, {}])
# With deprecated APIs, this is there.
ret = l1.rpc.sql("SELECT max_total_htlc_in_msat FROM peerchannels;")
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.