keel VS semantic-release

I just want to throw in keel as another alternative.

There are multiple tools available for that. Another one could be https://keel.sh

Flux for Kubernetes and we have installed Keel to let devs restart deployments on Development cluster. We don't use Webhooks but just have them do Powershell request to endpoint either in their pipeline or manually depending on dev teams desire.

Have you seen keel? https://github.com/keel-hq/keel I'm using it on very small projects with very simple delivery logic, so I'm not sure if it's gonna work out in your case, you can give it a try though.

There is also a 3rd party tool like Keel but it doesn't support Amazon ECR (Webhook problem with ECR).

This got a little off track... I don't have a problem. You have a problem! but TLDR; keel?

I’ve used keel to help me with this issue: https://keel.sh.

Keel might be of interest.

I've used Keel and more recently ArgoCD Image Updater (Using ArgoCD to manage deployments).

I'm trying to improve the security behind our release process, which uses semantic-release. During this process, it creates a change log which is committed to the repo, publishes a package and a few other things.

Conventional commits specification contains a set of rules for creating an explicit commit history, which makes it easier to write automated tools on top of, for example, semantic release. You can manually follow this convention in your project or use a tool to assist you, such as Commitizen.

When working with JavaScript projects, managing version numbers and commit messages is important for the maintainability of the project. Since 2020 I have been the main developer of Atomic Calendar Revive a highly customisable Home Assistant calendar card, I found maintaining versions and releases to be cumbersome until recently. In this article, I will introduce the commitizen and semantic-release packages for creation or appropriate commit messages and semantic versioning. I will also provide examples of how I am currently using these packages to streamline my release workflow and project maintenance.

To further streamline deployments, I introduced semantic-release. This tool automates commit tagging and tracks changes since the previous version. As a result, deployments now occur only when new tags are present, saving us valuable minutes.

If your projects ar made in javascript and related tools, I'd suggest you to check: semantic-release