hyperlink
release-plz
| hyperlink | release-plz | |
|---|---|---|
| 1 | 6 | |
| 160 | 655 | |
| - | - | |
| 6.7 | 9.7 | |
| 5 months ago | 2 days ago | |
| Rust | Rust | |
| MIT License | Apache License 2.0 |
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.
hyperlink
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
What are some alternatives?
actix-form-validation - Form Validation in Actix Web using validator crate.
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
megalinter - 🦙 Mega-Linter analyzes 49 languages, 22 formats, 21 tooling formats, excessive copy-pastes, spelling mistakes and security issues in your repository sources with a GitHub Action, other CI tools or locally. [Moved to: https://github.com/oxsecurity/megalinter]
kitsune - 🦊 (fast) ActivityPub-federated microblogging
library-loader - [Unofficial] Samacsys Library Loader for all platforms!
cargo-dist - 📦 shippable application packaging
cargo-chef - A cargo-subcommand to speed up Rust Docker builds using Docker layer caching.
SquireCore - The backend library used by Squire Tournament Services
cargo-install-favorites - Use the `cargo` command install our favorite crates
springtime - A framework for advanced Rust applications.
rust - Empowering everyone to build reliable and efficient software.
icu4x - Solving i18n for client-side and resource-constrained environments.