Skip to content
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

Cut 0.0.115 #2211

Merged
merged 2 commits into from
Apr 25, 2023
Merged

Conversation

TheBlueMatt
Copy link
Collaborator

Still need to come up with a release name, but here's draft release notes.

@TheBlueMatt TheBlueMatt added this to the 0.0.115 milestone Apr 21, 2023
@codecov-commenter
Copy link

codecov-commenter commented Apr 22, 2023

Codecov Report

Patch coverage has no change and project coverage change: -0.03 ⚠️

Comparison is base (f1761e0) 91.57% compared to head (82f36d8) 91.54%.

❗ Current head 82f36d8 differs from pull request most recent head dafa095. Consider uploading reports for the commit dafa095 to get more accurate results

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2211      +/-   ##
==========================================
- Coverage   91.57%   91.54%   -0.03%     
==========================================
  Files         104      104              
  Lines       51745    51745              
  Branches    51745    51745              
==========================================
- Hits        47386    47371      -15     
- Misses       4359     4374      +15     

see 6 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

@TheBlueMatt TheBlueMatt force-pushed the 2023-04-0.0.115-cut branch 2 times, most recently from 4f971d5 to ccaafa0 Compare April 22, 2023 02:26
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved
CHANGELOG.md Outdated Show resolved Hide resolved

## Security
* Transaction re-broadcasting is now substantially more aggressive, including a
new regular rebroadcast feature called on a timer from the
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"If the rebroadcast is called directly from ChainMonitor::rebroadcast_pending_claims, it can be invoked as a aggressive as every 30s on mobile” ?

Should we say it comes at the downside of inflating the feerate paid? Might be concerning if you’re not using Core’s fee estimator but relying on a mempool only fee estimator.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It doesnt inflate the feerate, we don't bump on rebroadcasts.

CHANGELOG.md Show resolved Hide resolved
`ChannelMonitor` on 0.0.114 or before may panic (#2059). Note that this is
in general unsupported, and included here only for completeness.

## Bug Fixes
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is #2161 a bug fix? Also #2145

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think 2161 is an API change, but included both, thanks.

Copy link
Contributor

@valentinewallace valentinewallace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM after squash

@TheBlueMatt
Copy link
Collaborator Author

Want to land #2220 first.

@TheBlueMatt
Copy link
Collaborator Author

Let's do #2004 as well.

@TheBlueMatt
Copy link
Collaborator Author

Rebased on #2004, updated release notes to include everything, added diff totals. Should be good to go!

@TheBlueMatt
Copy link
Collaborator Author

Rebased again, and added the one missing commit.

Copy link
Contributor

@dunxen dunxen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 🚀

@TheBlueMatt TheBlueMatt merged commit b734735 into lightningdevkit:main Apr 25, 2023
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.

6 participants