• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

tari-project / tari / 18160780951 / 1
62%
development: 62%

Build:
DEFAULT BRANCH: development
Ran 01 Oct 2025 12:40PM UTC
Files 700
Run time 30s
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

01 Oct 2025 11:31AM UTC coverage: 59.504% (-0.02%) from 59.527%
18160780951.1

push

github

web-flow
chore: add rust minimum version (#7522)

Description
---
- Added minimum supported Rust version as `rust-version` in the
workspace root and inherited it all in the member crates `Cargo.toml`
files. This will let cargo refuse to build on older compilers and will
ensure that the development environment will be synchronised with the
stable features enforced by the minimum supported compiler.
- Added consistent use of `[workspace.package]` inheritance for all the
member crates `cargo.toml` files where it applies.
- Fixed minor build errors due to the consistent use of `rust-version`
and `edition` in all member crates.
- Pinned the `minotari_ledger_wallet_common crate` to use `rust-version
= "1.85.0"`, which is compatible with the Docker `ledger-app-builder`,
to not inherit `rust-version` from the workspace.

Motivation and Context
---
See above.

How Has This Been Tested?
---
- Passed `cargo lints clippy --all-targets --all-features`.
- Passed `minotari_ledger_wallet` build test via Docker.

What process can a PR reviewer use to test or verify this change?
---
- `cargo lints clippy --all-targets --all-features`.
- `minotari_ledger_wallet` build test via Docker.

<!-- Checklist -->
<!-- 1. Is the title of your PR in the form that would make nice release
notes? The title, excluding the conventional commit
tag, will be included exactly as is in the CHANGELOG, so please think
about it carefully. -->


Breaking Changes
---

- [x] None
- [ ] Requires data directory on base node to be deleted
- [ ] Requires hard fork
- [ ] Other - Please specify

<!-- Does this include a breaking change? If so, include this line as a
footer -->
<!-- BREAKING CHANGE: Description what the user should do, e.g. delete a
database, resync the chain -->


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Chores**
* Standardized Rust toolchain (rust-version updated to 1.90 and
propagated to workspace) and moved many package metadata... (continued)

67413 of 113291 relevant lines covered (59.5%)

305644.71 hits per line

Source Files on job 18160780951.1
  • Tree
  • List 700
  • Changed 9
  • Source Changed 1
  • Coverage Changed 8
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Build 18160780951
  • 16bd6980 on github
  • Prev Job for on development (#18121503055.1)
  • Next Job for on development (#18223061931.1)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc