Skip to content

Fix deprecated APIs handling and update glightning dependency #392

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

YusukeShimizu
Copy link
Contributor

Remove the '--allow-deprecated-apis=true' flag
from the CLightningNode initialization in the test framework.

This will increase the possibility of detecting problems before they occur, as support for the deprecated cln api is no longer available.

Fixes #232

This PR addresses two deprecation issues:

1. Apply changes from ElementsProject#336
   - Add isDev parameter to CheckForDeprecatedApiConfig function
   - Skip deprecated API check in development mode
   - Remove --allow-deprecated-apis=true from test framework

2. Fix 'decodepay' deprecation error
   - Update glightning dependency to use PR ElementsProject/glightning#24
   - This PR adds support for the new 'decode' RPC command
   - Maintains backward compatibility with older CLN versions

The decodepay command was deprecated in CLN v24.11 in favor of the
more general decode command. This change ensures compatibility with
current and future CLN versions.

Depends on: ElementsProject/glightning#24
@YusukeShimizu YusukeShimizu force-pushed the fix-deprecated-apis-and-decodepay branch from e4a776c to 9690c25 Compare July 25, 2025 08:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Future CLN API deprecations can negatively affect PeerSwap
1 participant