Skip to content

Conversation

@nyonson
Copy link
Collaborator

@nyonson nyonson commented Jan 6, 2026

These changes make the api command more robust, been able to use it in the rust-psbt project as I explore different ways to break an exported API and see if this detects it. We might just have to drop these custom checks with cargo-semver-checks as discussed in #58, because this is quite the rabbit hole, but figure I'd give it the old college try and learn along the way.

I think this new rbmt.toml config for the api command will be helpful no matter what. It also lets a user opt-in to the semver checking, they have to set a baseline in the package config.

[api]
# Additional feature combinations to test (beyond no-features and all-features).
features = [
    ["alloc"]
]
# Optional: Git reference for semver compatibility checking.
baseline = "v1.0.0"

@nyonson nyonson force-pushed the configurable-api-features branch 2 times, most recently from aa5ff12 to 247d431 Compare January 6, 2026 18:12
Upgraded public-api crate from v0.47 to v0.50.2 to support more recent
nightly toolchain versions. The public-api versions only support a window
of nightly versions.

The new version of public-api uses edition 2024 which requires rust 1.85+
so the MSRV of cargo-rbmt was raised as well.
@nyonson nyonson force-pushed the configurable-api-features branch from d37f782 to c475f48 Compare January 8, 2026 20:50
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.

1 participant