Our great sponsors
-
-
cargo-release
Discontinued Cargo subcommand `release`: everything about releasing a rust crate. [Moved to: https://github.com/crate-ci/cargo-release] (by sunng87)
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
ripgrep
ripgrep recursively searches directories for a regex pattern while respecting your gitignore
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
In Doctests don't work in bin targets, non-public items #50784 QuietMisdreavus shows a way to run doc tests for a binary crate.
Between workspace inheritance and tools like cargo-release, this has become trivial for me. If people don't want to use a third-party tool, we can always be working on improving cargo further, like publishing more than one crate at a time or merging support for modifying versions.
Between workspace inheritance and tools like cargo-release, this has become trivial for me. If people don't want to use a third-party tool, we can always be working on improving cargo further, like publishing more than one crate at a time or merging support for modifying versions.
tools like cargo-release
Thank you for plugging cargo release here. I feel like I looked at it long ago (years? maybe a different tool with a similar name?) and it didn't seem like it would carry its weight. But my release checklist for ripgrep is incredibly annoying and tedious. I'll see if I can give cargo release a whirl the next time I do a ripgrep release. I'll be excited if it can automate most of it. The biggest pain is having to update minimum version numbers in dependents.