|
| 1 | +--- |
| 2 | +title: "Updatecli v0.100.0: A Milestone in Continuous Delivery" |
| 3 | +date: 2025-05-14T00:00:00+00:00 |
| 4 | +draft: false |
| 5 | +weight: 50 |
| 6 | +images: [""] |
| 7 | +contributors: ["olblak"] |
| 8 | +--- |
| 9 | + |
| 10 | +We just released Updatecli version **[v0.100.0](https://www.updatecli.io/changelogs/updatecli/changelogs/v0.100.0/)**! |
| 11 | +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. |
| 12 | + |
| 13 | +Very early on, we automated the release process using **GitHub Actions**, **GoReleaser**, and of course, **Updatecli** itself. |
| 14 | +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. |
| 15 | + |
| 16 | +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. |
| 17 | + |
| 18 | +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. |
| 19 | + |
| 20 | +## The Challenge of Frequent Releases |
| 21 | + |
| 22 | +However, frequent releases also come with a challenge: **communication**. |
| 23 | +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. |
| 24 | + |
| 25 | +To address this, about a year ago we started an experiment: **automatically publishing release notes to the Updatecli website**: |
| 26 | + |
| 27 | +📄 [Changelogs on updatecli.io](https://www.updatecli.io/changelogs/updatecli/) |
| 28 | + |
| 29 | +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. |
| 30 | + |
| 31 | +If you're curious about how we generate those release notes, check out this post: |
| 32 | + |
| 33 | +📝 [Welcome Releasepost](https://www.updatecli.io/blog/welcome-releasepost/) |
| 34 | + |
| 35 | +## What’s Next |
| 36 | + |
| 37 | +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. |
| 38 | + |
| 39 | +If you have feedback or ideas on how we can improve, I'd love to hear them! |
| 40 | + |
| 41 | +## What about v0.100.0 |
| 42 | + |
| 43 | +### 🛠️ GitLab Merge Request Enhancements |
| 44 | + |
| 45 | +You can now configure additional fields—such as labels, assignees, and more—when creating merge requests via GitLab using Updatecli. |
| 46 | +Thanks to [@alikhil](https://github.com/alikhil) for this contribution! |
| 47 | +👉 Makes Updatecli more flexible for GitLab-based CI/CD workflows. |
| 48 | + |
| 49 | +### 📦 Cargo Autodiscovery Improvement |
| 50 | + |
| 51 | +Updatecli's Cargo autodiscovery now uses `cargo-upgrade` instead of `cargo update` to handle Rust dependency updates. |
| 52 | +Thanks to [@loispostula](https://github.com/loispostula)! |
| 53 | +👉 Preserves formatting of `Cargo.toml` files and improves semver handling. |
| 54 | + |
| 55 | +## Updatecli by the Numbers |
| 56 | + |
| 57 | +As of today: |
| 58 | + |
| 59 | +**⭐ GitHub Stars**: 700 |
| 60 | +**🥳 Contributors**: 60+ |
| 61 | +**⬇️ Total Download stats**: 111585 |
| 62 | +**⬇️ v0.99.0 Download stats (released one week ago)**: 14364 |
| 63 | + |
| 64 | +--- |
| 65 | +[_Source: GitHub Release Artifacts_](https://somsubhra.github.io/github-release-stats/?username=updatecli&repository=updatecli&page=1&per_page=5) |
| 66 | + |
| 67 | + checksums.txt - downloaded 101 times. Last updated on 2025-05-05 |
| 68 | + checksums.txt.pem - downloaded 13 times. Last updated on 2025-05-05 |
| 69 | + checksums.txt.sig - downloaded 13 times. Last updated on 2025-05-05 |
| 70 | + updatecli_amd64.deb - downloaded 134 times. Last updated on 2025-05-05 |
| 71 | + updatecli_amd64.rpm - downloaded 1 time. Last updated on 2025-05-05 |
| 72 | + updatecli_arm64.deb - downloaded 118 times. Last updated on 2025-05-05 |
| 73 | + updatecli_Darwin_arm64.tar.gz - downloaded 94 times. Last updated on 2025-05-05 |
| 74 | + updatecli_Darwin_arm64.tar.gz.sbom.json - downloaded 1 time. Last updated on 2025-05-05 |
| 75 | + updatecli_Darwin_x86_64.tar.gz - downloaded 50 times. Last updated on 2025-05-05 |
| 76 | + updatecli_Linux_arm.tar.gz - downloaded 2 times. Last updated on 2025-05-05 |
| 77 | + updatecli_Linux_arm64.tar.gz - downloaded 2023 times. Last updated on 2025-05-05 |
| 78 | + updatecli_Linux_x86_64.tar.gz - downloaded 11447 times. Last updated on 2025-05-05 |
| 79 | + updatecli_Windows_arm.zip - downloaded 0 times. Last updated on 2025-05-05 |
| 80 | + updatecli_Windows_arm64.zip - downloaded 5 times. Last updated on 2025-05-05 |
| 81 | + updatecli_Windows_x86_64.zip - downloaded 177 times. Last updated on 2025-05-05 |
| 82 | + |
| 83 | +--- |
| 84 | + |
| 85 | +<p align="center"> |
| 86 | + <img src="/images/blog/2025/05/updatecli.io.png" /> |
| 87 | +</p> |
| 88 | + |
| 89 | +These numbers aren’t just stats—they reflect the growing community around Updatecli. |
| 90 | +Thank you to everyone who's contributed, tested, reported issues, or simply used it in their pipeline! |
| 91 | + |
| 92 | +Want to get involved? Check out our [contributing guide](https://github.com/updatecli/updatecli?tab=readme-ov-file#contributing) or open an issue—we’d love your input. |
0 commit comments