[r1ckstardev]

Update both Core Lightning test nodes from v26.06.1 to v26.06.10, so the integration suite covers this security release before the deployment image is advanced.

The image is built from basedon-v26.06.10. The release workflow and its downstream test gates are documented in btcpayserver/lightning#5.

[coderabbitai]

No actionable comments were generated in the recent review.

Walkthrough

The test Compose configuration updates the image tag for lightningd and lightningd_dest from v26.06.1 to v26.06.10.

Changes: Lightning test images

Layer / File(s)	Summary
Update Lightning image tags tests/docker-compose.yml	The lightningd and lightningd_dest services now use image tag v26.06.10.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Change: Other

Merge Risk: Minimal · up to 2572f

Both Lightning test services now reference the published v26.06.10 image. The image-availability concern is disproved, and this change is mergeable subject to normal checks.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly states that the Core Lightning test images are updated to v26.06.10. It matches the main change.
Description check		The description directly explains the image update, the security-release objective, and the affected test nodes. It is related to the changeset.
Docstring Coverage		No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

Finishing Touches

Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Tip

🎯 Customize your risk assessments

Guide how CodeRabbit assesses merge risk and security architecture risk. Highlight sensitive changes and explain your security boundaries using Merge Risk Instructions and Security Risk Instructions in your review settings. Security architecture risk assessments require the Advanced plan or above.

✅ Automatic approvals, with your rules

Let CodeRabbit approve pull requests once required threads are resolved, pre-merge checks pass, and your risk limits are met. Enable Automatic approvals in review settings, with overrides for teams or file paths.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

• X
• Mastodon
• Reddit
• LinkedIn

_{A rabbit checks the tags in place
Two Lightning images match the pace
The compose file now points ahead
With v26.06.10 instead
I twitch my nose and hop away}

Recent review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: CHILL
• Plan: Advanced
• Run ID: 4da8b8ee-de15-40c0-ba7d-2b1799c6c31e

Commits

Reviewing files that changed from the base of the PR and between 889ea23 and 2572f3f.

Files selected for processing: 1

• tests/docker-compose.yml

Included review availability: This review used your included allowance. Your plan provides up to 2 included reviews per hour; 1 remain after this review.