Updatecli v0.100.0: A Milestone in Continuous Delivery
Posted May 14, 2025 by olblak ‐ 3 min read
We just released Updatecli version v0.100.0! While hitting version 100 feels like a milestone, the truth is even more impressive: we’ve published 206 releases since the beginning of the project, 5 years ago.
Very early on, we automated the release process using GitHub Actions, GoReleaser, and of course, Updatecli itself. This setup allows us to publish all artifacts from various Git repositories with just a few clicks—right from GitHub. It also means that other core contributors can trigger releases even when I’m not available, helping the project stay agile.
This level of automation allows us to move quickly. I usually try to merge community PRs promptly and aim to publish a new release within the same week.
Stability remains a top priority—when something goes wrong, we revert the problematic PR and cut a new release. It has happened a few times, but thankfully, we’ve always been able to identify and fix the issues quickly.
The Challenge of Frequent Releases
However, frequent releases also come with a challenge: communication. With so many updates, it’s easy for changes to get lost. Sometimes, users ask for features that have already been implemented—they just weren’t aware.
To address this, about a year ago we started an experiment: automatically publishing release notes to the Updatecli website:
The goal was to improve the visibility of each release. While I don’t yet have a reliable way to measure its effectiveness, I do see some traffic in the updatecli.io website analytics, so it seems to be helping.
If you’re curious about how we generate those release notes, check out this post:
What’s Next
Looking ahead, I believe we can do a better job of summarizing the overall evolution of the project—something more digestible for users who don’t follow every release.
If you have feedback or ideas on how we can improve, I’d love to hear them!
What about v0.100.0
🛠️ GitLab Merge Request Enhancements
You can now configure additional fields—such as labels, assignees, and more—when creating merge requests via GitLab using Updatecli.
Thanks to @alikhil for this contribution!
👉 Makes Updatecli more flexible for GitLab-based CI/CD workflows.
📦 Cargo Autodiscovery Improvement
Updatecli’s Cargo autodiscovery now uses cargo-upgrade instead of cargo update to handle Rust dependency updates.
Thanks to @loispostula!
👉 Preserves formatting of Cargo.toml files and improves semver handling.
Updatecli by the Numbers
As of today:
⭐ GitHub Stars: 700
🥳 Contributors: 60+
⬇️ Total Download stats: 111585
⬇️ v0.99.0 Download stats (released one week ago): 14364
Source: GitHub Release Artifacts
checksums.txt - downloaded 101 times. Last updated on 2025-05-05
checksums.txt.pem - downloaded 13 times. Last updated on 2025-05-05
checksums.txt.sig - downloaded 13 times. Last updated on 2025-05-05
updatecli_amd64.deb - downloaded 134 times. Last updated on 2025-05-05
updatecli_amd64.rpm - downloaded 1 time. Last updated on 2025-05-05
updatecli_arm64.deb - downloaded 118 times. Last updated on 2025-05-05
updatecli_Darwin_arm64.tar.gz - downloaded 94 times. Last updated on 2025-05-05
updatecli_Darwin_arm64.tar.gz.sbom.json - downloaded 1 time. Last updated on 2025-05-05
updatecli_Darwin_x86_64.tar.gz - downloaded 50 times. Last updated on 2025-05-05
updatecli_Linux_arm.tar.gz - downloaded 2 times. Last updated on 2025-05-05
updatecli_Linux_arm64.tar.gz - downloaded 2023 times. Last updated on 2025-05-05
updatecli_Linux_x86_64.tar.gz - downloaded 11447 times. Last updated on 2025-05-05
updatecli_Windows_arm.zip - downloaded 0 times. Last updated on 2025-05-05
updatecli_Windows_arm64.zip - downloaded 5 times. Last updated on 2025-05-05
updatecli_Windows_x86_64.zip - downloaded 177 times. Last updated on 2025-05-05
These numbers aren’t just stats—they reflect the growing community around Updatecli. Thank you to everyone who’s contributed, tested, reported issues, or simply used it in their pipeline!
Want to get involved? Check out our contributing guide or open an issue—we’d love your input.