https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/contributors/olblak/Recent content in Olblak onHugo -- gohugo.ioen-USTue, 06 Oct 2020 08:50:45 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/securing-github-actions-workflows-with-zizmor-scaling-using-updatecli/Fri, 13 Mar 2026 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/securing-github-actions-workflows-with-zizmor-scaling-using-updatecli/Recent incidents have shown that weak GitHub Actions workflows can lead to repository compromise. A great tool to prevent this is Zizmor, a static analysis tool for GitHub Actions. As the Zizmor project states: Zizmor can find many common security issues in typical GitHub Actions CI/CD setups, including: Template injection vulnerabilities, leading to attacker-controlled code execution Accidental credential persistence and leakage Excessive permission scopes and credential grants to runners Impostor commits and confusable git references …and much more!https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/what-a-year-2025-has-been-see-you-in-2026/Wed, 31 Dec 2025 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/what-a-year-2025-has-been-see-you-in-2026/It’s time to close another great year on the Updatecli journey. This year we achieved 29 releases contributed by over 20 community members. It wouldn’t be possible to list all the improvements in this post, so feel free to take a look to our website for a detailed list of changes on updatecli.io And not only did we continue consolidating and improving Updatecli, we also experimented with new ideas. External Plugin Ecosystem # For example, defining update strategies in YAML is convenient, saves time, and helps teams collaborate.https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/updatecli-v0.110.0-released-github-search-scm-git-branch-cleanup-dockerfile-matching-and-more/Wed, 05 Nov 2025 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/updatecli-v0.110.0-released-github-search-scm-git-branch-cleanup-dockerfile-matching-and-more/We’re excited to ship v0.110.0 — this release introduces a GitHub search SCM to target multiple repositories, improved Git branch handling (including optional cleanup of working branches), better Dockerfile matching behavior, and a handful of bug fixes and quality-of-life improvements. Highlights # New githubsearch SCM kind to discover and operate on repositories matching a GitHub search query. New --clean-git-branches flag to remove Updatecli working branches that have no divergent changes. Git pushes are now collected and executed once (after all targets) to reduce CI noise and enable reliable branch cleanup.https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/automating-golang-project-updates-with-updatecli/Fri, 24 Oct 2025 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/automating-golang-project-updates-with-updatecli/Please note that this post is not an introduction to Updatecli but rather an overview of specific Updatecli uses cases for Golang related projects. If you are new to Updatecli, please start with Getting Started with Updatecli. With that being said, let’s dive in. Keeping your Go projects up to date—whether it’s module versions, replace directives, or the Go toolchain version—can be tedious and error-prone, especially as your codebase grows or you manage multiple repositories.https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/updatecli-v0.109.0-released-github-app-auth-smarter-npm-cargo-autodiscovery-and-more/Mon, 13 Oct 2025 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/updatecli-v0.109.0-released-github-app-auth-smarter-npm-cargo-autodiscovery-and-more/I am excited to announce the release of Updatecli v0.109.0, packed with new features and improvements that make dependency automation even more powerful and secure. This release brings major enhancements to GitHub authentication, NPM and Cargo autodiscovery, and overall developer experience. You can find the full release notes on updatecli.io Otherwise, read on for the highlights of this release! 🚀 Highlights # 1. GitHub App Support for GitHub Authentication # Updatecli now supports GitHub App authentication!https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/updatecli-v0.100.0-a-milestone-in-continuous-delivery/Wed, 14 May 2025 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/updatecli-v0.100.0-a-milestone-in-continuous-delivery/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.https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/highlight-of-the-week/Mon, 29 Jul 2024 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/highlight-of-the-week/What a great way to start the week by not discovering one but two blog posts about Updatecli. The first one I discovered, was written by Sean Rigby on blog.devgenius.io It highlights the Autodiscovery feature of Updatecli, and how flexible it can be to discover updates in GitOps repositories automatically. In the blogpost Sean covers ArgoCD, but Updatecli also takes care of FluxCD or Rancher Fleet GitOps repositories. The second one on write.https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/updatecli-survey/Fri, 12 Jul 2024 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/updatecli-survey/Getting feedback on an OSS project is hard. Most of the time, we can only rely on people reporting issues, which tell us little about what we are doing right or what we should focus on. To better understand your experience with the Updatecli project, we’d love for you to participate in our Updatecli survey: The survey is anonymous and all questions are optional. Thanks in advance for your help.https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/welcome-releasepost/Thu, 23 May 2024 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/welcome-releasepost/No matter the project I am working on, I am constantly looking for project release notes. The good news is we now have access to great tools to automatically generate those release notes such as Release Drafter, Changie, Conventional Changelog, etc. In 2024, there is no excuse to skip that critical piece of information. The sad news is that I now spend a significant amount of time searching for those release notes on platforms like GitHub…https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/shareable-policies/Tue, 13 Feb 2024 00:00:00 +0000https://deploy-preview-2800--amazing-golick-2d0138.netlify.app/blog/shareable-policies/Time flies, and It’s time for another successful experiment to go out. Shareable Update Policies A recurring problem over time has been, how to reuse the same Updatecli manifests for different projects. From the beginning of the Updatecli project, it was possible to parameterize Updatecli manifests using values or secrets files, but still, we had to copy the same Updatecli manifest over and over. This led to duplication, maintenance burden, and ultimately, It didn’t scale well.