codecov-commenter
commented
5 months ago Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 84.85%. Comparing base (
0dd6dad) to head (9abd877).
Additional details and impacted files
```diff @@ Coverage Diff @@ ## master #243 +/- ## ======================================= Coverage 84.85% 84.85% ======================================= Files 17 17 Lines 2192 2192 ======================================= Hits 1860 1860 Misses 332 332 ``` | [Flag](https://app.codecov.io/gh/LedgerHQ/app-bitcoin-new/pull/243/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=LedgerHQ) | Coverage Δ | | |---|---|---| | [unittests](https://app.codecov.io/gh/LedgerHQ/app-bitcoin-new/pull/243/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=LedgerHQ) | `84.85% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=LedgerHQ#carryforward-flags-in-the-pull-request-comment) to find out more.:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
sonarcloud[bot]
Fixes an issue reported by @wizardsardine: signing fails in taproot policies for keys that have derivations not ending with
/<0;1>/*, due to the wrong derivation path being used during the computation of the tapleaf hash at signing time.Prepares release 2.2.1 to release the fix asap.