release-plz
cargo-binstall
| release-plz | cargo-binstall | |
|---|---|---|
| 6 | 24 | |
| 659 | 1,313 | |
| - | 5.5% | |
| 9.7 | 9.5 | |
| 7 days ago | 4 days ago | |
| Rust | Rust | |
| Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
release-plz
-
Changelog-Driven Releases
My problem with maintaining a changelog during development is it can serve as a source of merge conflicts. Instead, I follow Covnentional Commit style and manually write my changelog entries based on the commits. I have a tool [0] that can show me the relevant commits for a package in my repo and automates the entire release process, including doing sanity checks.
I also feel like releasing from CI is hard, especially if you have multiple packages in a repo [1], including
- You can't as easily introspect the process
- You can't as easily recover from failure
- Getting a lot of the nuance right, like handling releases concurrent to merging of PRs, is difficult
- When the workflow is an ever-present "release PR" that you merge when ready has issues with selecting which packages to release and at what version
I have been considering making a tool to generate changelogs from fragments. Been keeping notes at https://github.com/epage/epage.github.io/issues/23
[0]: https://github.com/crate-ci/cargo-release
[1]: https://github.com/MarcoIeni/release-plz/discussions/1019
- Release Rust Crates from CI with a Release PR
-
Any new Opensource projects in (rust) looking for contributors. I want to start my journey as an OSS contributor.
Hi 👋 I maintain release-plz, a project enabling maintainers to release Rust packages automatically.
-
Release engineering is exhausting so here's cargo-dist
How does this tool differ from release-plz?: https://github.com/marcoIeni/release-plz
-
GitHub action for version incrementing and publishing to crates.io in single click
Nice, very simple. I like it! You might also want to check out my project: https://github.com/MarcoIeni/release-plz
- Announcing release-plz: update the version of your packages automatically based on conventional commits
cargo-binstall
-
Cargo Binstall 1.0.0 release
Unfortunately not really usable in production (for me) until https://github.com/cargo-bins/cargo-binstall/issues/1 is fixed :( Really much looking forward to it though, as I think it's a great addition to the Rust ecosystem!
-
Oxidise your Infrastructure using Shuttle.rs
Oh looks like cargo-binstall is currently broken (https://github.com/cargo-bins/cargo-binstall/issues/1094)
-
Ludusavi can now back up your game saves to the cloud and detect Lutris saves
Unfortunately, I ended up running into an issue with the zip support, but I'll come back to it once this is fixed: https://github.com/cargo-bins/cargo-binstall/issues/1080
-
Strange lifetime error: Requires to be `'static`
I've encountered a strange lifetime error when developing new features in cargo-binstall:
-
AMDGPU_TOP - tool to show AMDGPU usage
Once you feel like releasing it, could you please add binstall support?
-
[rcargo] quick tool for faster crate building on remote workstations
I think in a similar vein there is cargo-binstall that is a cargo install alternative that attempts to use pre-built binary artifacts when possible
-
Faster Apple Builds with the lld Linker
I hope ld64 and lld add supports for plugin-opt I'm trying to enable cross-lang-lto on MacOS but failed due to -plugin-opt not supported.
-
Install a CLI in a project (not globally)
You can use cargo-binstall --install-path to install binaries to custom locations.
-
Release engineering is exhausting so here's cargo-dist
If you happen to install a lot of things with cargo, check out cargo-binstall: https://github.com/cargo-bins/cargo-binstall
It'll fetch the binary release from the repo so you don't have to compile it yourself.
-
Thoughts about updating a rust cli via a sub command for improved dev experience
I'd recommend to use cargo-binstall, which can download pre-built artifacts from github release.
What are some alternatives?
websurfx - :rocket: An open source alternative to searx which provides a modern-looking :sparkles:, lightning-fast :zap:, privacy respecting :disguised_face:, secure :lock: meta search engine
pwninit - pwninit - automate starting binary exploit challenges
kitsune - 🦊 (fast) ActivityPub-federated microblogging
cargo-quickinstall - pre-compiled binary packages for `cargo install` [Moved to: https://github.com/cargo-bins/cargo-quickinstall]
cargo-dist - 📦 shippable application packaging
ez_term - Terminal UI framework based on templates and focused on simplicity.
SquireCore - The backend library used by Squire Tournament Services
nue - I/O and binary data encoding for Rust
cargo-install-favorites - Use the `cargo` command install our favorite crates
docker-cargo-binstall
springtime - A framework for advanced Rust applications.
amdgpu_top - Tool to display AMDGPU usage