SquireCore
release-plz
| SquireCore | release-plz | |
|---|---|---|
| 3 | 6 | |
| 21 | 655 | |
| - | - | |
| 9.1 | 9.7 | |
| 3 months ago | 4 days ago | |
| Rust | Rust | |
| GNU Affero General Public License v3.0 | 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.
SquireCore
- First project in Rust suggest a better one please
- Any new Opensource projects in (rust) looking for contributors. I want to start my journey as an OSS contributor.
-
What’s everyone working on this week (33/2022)?
I'll be working on what I've been working on for a while, SquireCore, an open source tournament management software geared toward Magic: the Gathering (and likely it's application in it's Discord bot).
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?
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
SquireBot - A Discord bot to help run tournaments
kitsune - 🦊 (fast) ActivityPub-federated microblogging
lemmeknow - The fastest way to identify anything!
cargo-dist - 📦 shippable application packaging
comet - Comet, Stellar Pup simulator
cargo-install-favorites - Use the `cargo` command install our favorite crates
tictactoe
springtime - A framework for advanced Rust applications.
hexerator - Versatile GUI hex editor focused on binary file exploration and aiding pattern recognition
rust - Empowering everyone to build reliable and efficient software.