meta: fix cln version to 24.05 #127
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vincenzopalazzo
force-pushed
the
macros/cln-version-pin
branch
from
eb65cc7 to
6696c40
Compare
cln version 24.05 is the last version of core lightning that it is working with the version of prototest. Most lickly this is a cln bug described in the following issue [1]. However, we pin the cln version and report the bug to mainline probably someone will be able to find the real issue in the cln or lnprototest at some point. [1] #123 Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
vincenzopalazzo
force-pushed
the
macros/cln-version-pin
branch
from
6696c40 to
6386bb7
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
cln version 24.05 is the last version of core lightning that it is
working with the version of prototest. Most lickly this is a cln
bug described in the following issue [1].
However, we pin the cln version and report the bug to mainline probably
someone will be able to find the real issue in the cln or lnprototest
at some point.
[1] #123