|
Ran
|
Jobs
1
|
Files
22
|
Run time
1min
|
Badge
README BADGES
|
push
github
Merge bitcoindevkit/bdk_wallet#215: Chore: migrate library version naming convention on master <a class=hub.com/bitcoindevkit/bdk_wallet/commit/<a class="double-link" href="https://git"><a class=hub.com/bitcoindevkit/bdk_wallet/commit/1022fce38447ba8c09a6ff8efc3295f0257c7bd1">1022fce38 chore: migrate library version naming convention on master (thunderbiscuit) Pull request description: This PR implements the discussion started on #19, as well as discussions over a few dev calls. The preferred approach is the one used by [rust-bitcoin](https://github.com/rust-bitcoin/rust-bitcoin/blob/master/bitcoin/Cargo.toml). ### Notes to the reviewers The core workflow for this is to keep the version on the master branch always an `alpha.0`, and simply update it to the next planned release once a branch has been created for a release. So for example, the master branch could be on `1.3.0-alpha.0` until the branch for 1.3.0 is cut, at which moment the master moves on to `1.4.0-alpha.0`. Someone pulling the master branch is always building one of those `-alpha.0` versions. ### Changelog notice None. ### Checklists #### All Submissions: * [x] I've signed all my commits * [x] I followed the [contribution guidelines](https://github.com/bitcoindevkit/bdk/blob/master/CONTRIBUTING.md) * [x] I ran `cargo fmt` and `cargo clippy` before committing ACKs for top commit: oleonardolima: ACK 1022fce38447ba8c09a6ff8efc3295f0257c7bd1 notmandatory: ACK 1022fce38447ba8c09a6ff8efc3295f0257c7bd1 Tree-SHA512: d17583871c9d6047111e4dda45e0ee3c359
7266 of 8442 relevant lines covered (86.07%)
3498.46 hits per line
| ID | Job ID | Ran | Files | Coverage | |
|---|---|---|---|---|---|
| 1 | 14918516514.1 | 22 |
86.07 |
GitHub Action Run |
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line |
|---|