payany: upgrade to v0.3.0 #678
Merged
Conversation
This file contains hidden or 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
chrisguida approved these changes Jul 22, 2025
Collaborator
chrisguida left a comment
chrisguida left a comment There was a problem hiding this comment.
LGTM
ACK da5d41c
There are some flaky tests due to GH ratelimiting its API, @daywalker90 is working on a workaround.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
2 participants
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.
[0.3.0] 2025-07-07
Removed
payany-dns: option removed (you have to remove it from your config if you have set it!) in favor of trying them all one by one and using CLN'sproxyif it is configured toalways-use-proxyChanged
proxyif it is configured andalways-use-proxyis set totrueAdded
[0.2.5] 2025-04-17
Fixed
payany-xpay-handle-pay: wallets sendingmaxfeepercentas a string now work as expected