NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules, #1132 by repository stars
Latest stable
v1.5.0
Last release 8 days ago
14 Nov 2026
Ships fairly regularly
a new release about every 9 days
Nearly every release is documented
notes for 60 of 60 stable releases
Nothing withdrawn
no release was ever pulled
6 years old
453 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Upgrade dependencies for fix vulnerabilities by @vsychov in https://github.com/argoproj-labs/argocd-image-updater/pull/599
Full Changelog: https://github.com/argoproj-labs/argocd-image-updater/compare/v0.12.2...v0.13.0
Minor bug fix release for the 0.12 release branch to support additional OCI media type in registries and updates Golang and some dependencies.
Minor bug fix release for the 0.12 release branch to support additional OCI media type in registries and updates Golang and some dependencies.
N/A
N/A
fix: update application config sample & replace the deprecated ioutil pkg
Minor bug fix release for the 0.12 release branch, which missing ca-certs in docker image
N/A
N/A
This release also has potentially breaking changes, please read the upgrade notes below.
The version v0.12.0 is a feature release, bringing some new features as well as bug fixes to Argo CD Image Updater. This release also has potentially breaking changes, please read the upgrade notes below.
We are very sorry for the delay with this release! Behind the scenes. we also worked on improving the documentation and gave it some refactoring. We hope you like it!
Multi-arch deliverables are finally here! We now provide container images for linux/amd64 and linux/arm64, as well as release binaries for linux/amd64, linux/arm64, linux/ppc64le, darwin/amd64, darwin/arm64 as well as windows/amd64!
Multi-arch support for container images: Argo CD Image Updater now also considers the architecture of container images and provides full support for multi-arch images by being able to inspect manifest lists. By default, when using an update strategy that supports meta data inspection (latest and digest), Argo CD Image Updater will now only consider manifests for the same architecture it is running on. This can be fine tuned on a per image basis, so if you have clusters with nodes spanning multiple architectures (e.g. mix of amd64 and arm64 nodes), and you know that certain workloads are bound to run on a given architecture, you can use the new <alias>.platforms annotation to allow only updates to images that match a certain architecture.
Less configuration need for registries: Argo CD Image Updater now requires even less configuration, even if used with custom registries, and supports more registries out of the box. Argo CD Image Updater will infer the registry API to use from an image's registry prefix. Now custom registries need only be configured in special cases, e.g. when the registry uses a self-signed certificate or when you want to configure global credentials, or fine tune other access parameters such as rate limiting.
Improved support for the digest update strategy: For multi-arch images, the digest update strategy will set the image SHA to the SHA of the manifest list, so the node can pick the right architecture to deploy. Also, Argo CD Image Updater will now perform less requests to the registry when using the digest update strategy, resulting in happier rate limiters.
Improved documentation: We heard the community that our docs are complicated and hard to understand or follow. There has been a major refactoring of the docs to provide a better user experience, and we'll continuously work to improve them going forward.
Support for HTTP proxies: When accessing container registries, Argo CD Image Updater now honors the HTTP proxy configuration from the environment (i.e. http_proxy, https_proxy and no_proxy variables) and performs any HTTP requests through the configured proxies.
Application selection using labels: Now you can restrict Argo CD Image Updater to not only match on the names of applications, but also using a label matcher.
The Argo Project would like to thank the following people for their awesome contributions that made this release possible:
@agorgl @atarax @derdanne @iamnoah @jaideepr97 @jannfis @janpieper @janpieper-gcx @joebowbeer @joyrex2001 @katainaka0503 @manivannan-g @martin-marko @nick-homex @NickLarsenNZ @pacoguzman @patrykwozinski @zimbres @zoonoo
And also thanks to everyone who took the time to open and discuss issues.
This release has a few potentially breaking changes. Please review the below descriptions
Configuration details for the default registry have changed:
If you had previously configured a custom default registry (e.g. by setting prefix to the empty string in the registries configuration), it will not be assumed the default registry automatically anymore. You need to explicitly set the configuration property default to true in order for Argo CD Image Updater to pick this registry as the default one. Also, you should set the prefix property from the empty string to the true prefix of the registry.
Registry configuration property tagsortmode has been deprecated:
The tagsortmode configuration has been more confusing than helpful in the past, and is a relict from old times when Argo CD Image Updater wasn't able to inspect an image's meta data properly. This setting has now been deprecated and should not be used anymore. A warning will be printed when this is set for a registry, and the setting will be removed completely in a future version of Argo CD Image Updater.
Tagging of images using the digest update strategy has changed slightly: Argo CD Image Updater now uses a tag in the format <tagname>@sha256:<sha_of_digest> when setting image tag parameters. Previously, it had a slightly different format that often required workarounds when being used with Helm. If you are using such a workaround when rendering image specification in Helm, you should revisit your template and adapt it to the new format.
test command uses host platform by default: If you are running the argocd-image-updater test command from a system which is based on a different platform than your cluster, you will have to specify the cluster's platform using the --platforms option, otherwise results may not be the same as on the cluster.
Minor bug fix release for the 0.11 release branch, which fixes a small bug with TLS when fetching registry auth tokens.
Minor bug fix release for the 0.11 release branch, which fixes a small bug with TLS when fetching registry auth tokens.
N/A
N/A
Minor bug fix release for the 0.11 release branch, which fixes an annoyance with the digest update strategy and updates the base images used in the di
Minor bug fix release for the 0.11 release branch, which fixes an annoyance with the digest update strategy and updates the base images used in the distribution container image.
N/A
N/A
Bug fix release for the 0.11 release branch, which fixes an authentication bug and issues with JFrog Artifactory registries.
Bug fix release for the 0.11 release branch, which fixes an authentication bug and issues with JFrog Artifactory registries.
N/A
N/A
N/A
The version v0.11.0 is a minor feature release, bringing some new features as well as bug fixes to Argo CD Image Updater.
The version v0.11.0 is a minor feature release, bringing some new features as well as bug fixes to Argo CD Image Updater.
docker-registry-client by Docker's more modern distribution/v3 API.The Argo Project would like to thank the following people for their awesome contributions that made this release possible:
And also thanks to everyone who took the time to open and discuss issues.
No special instructions this time.
Bug fix release for the 0.10 release branch, which fixes some annoying issues with Kustomize applications.
Bug fix release for the 0.10 release branch, which fixes some annoying issues with Kustomize applications.
N/A
N/A
N/A
The version v0.10.2 is a patch release, and brings the aws CLI into the container image due to popular demand.
The version v0.10.2 is a patch release, and brings the aws CLI into the container image due to popular demand.
No special instructions this time.
None
None
The version v0.10.1 is a maintenance release updating the used base image only to address some vulnerabilities in Alpine.
The version v0.10.1 is a maintenance release updating the used base image only to address some vulnerabilities in Alpine.
No special instructions this time.
None
None
The version v0.10.0 brings a couple of new and exciting features as well as bug fixes to Argo CD Image Updater.
The version v0.10.0 brings a couple of new and exciting features as well as bug fixes to Argo CD Image Updater.
Major new features:
New digest update strategy: This update strategy lets you track the most recent pushed version a single tag, e.g. latest. Image Updater will compare the SHA256 sum of the currently running image to the SHA256 sum of the image in the registry, and update if appropriate.
Modify kustomization.yaml directly: In addition to persisting the changes in the parameter overrides, Argo CD Image Updater can now modify a kustomization.yaml directly in order to update the image.
Custom Git commit messages: Users can now specify a custom Git commit message using Go string templates.
Start with empty image: Argo CD Image Updater is now able to update applications that have no initial image tag specified.
The Argo Project would like to thank the following people for their awesome contributions that made this release possible:
No special instructions this time.
Bug fix release for the 0.9 release branch, which fixes a race condition bug.
Bug fix release for the 0.9 release branch, which fixes a race condition bug.
N/A
N/A
N/A
Bug fix release for the 0.9 release branch, which fixes a bug in the manifests of v0.9.3
Bug fix release for the 0.9 release branch, which fixes a bug in the manifests of v0.9.3
N/A
N/A
N/A
Bug fix release for the 0.9 release branch, which fixes a bug related to Git write-back and Helm parameters.
Bug fix release for the 0.9 release branch, which fixes a bug related to Git write-back and Helm parameters.
N/A
N/A
N/A
Bug fix release for the 0.9 release branch, which fixes a few bugs related to Git write-back and the latest update strategy.
Bug fix release for the 0.9 release branch, which fixes a few bugs related to Git write-back and the latest update strategy.
Thanks to @magmax and @eplightning for reporting these issues and also for providing the related fixes.
N/A
N/A
N/A
Bug fix release for the 0.9 release branch, which fixes a serious problem with Git write-back.
Bug fix release for the 0.9 release branch, which fixes a serious problem with Git write-back.
N/A
N/A
N/A
We're happy to announce that starting with release v0.9.0, support for persisting changes to Git was added. Please be aware that using the Git write b
We're happy to announce that starting with release v0.9.0, support for persisting changes to Git was added. Please be aware that using the Git write back feature will require Argo CD v2.0 and upwards.
Also, we are working towards a more "zero-conf" approach. For this, we have introduced a new way for interacting with Argo CD using the Kubernetes API. This removes the previous requirement of having to change your Argo CD configuration (e.g. creating a user, RBAC rules, etc) and we hope will make integration much easier for our users. This also has become the default. In order to use the Argo CD API, the --applications-api parameter must be explicitly set to argocd.
Upgrade from v0.8.0 is attached with a couple of required actions, please see below.
Attention: By default, argocd-image-updater now uses the K8s API to retrieve applications, instead of the Argo CD API. Also, it is now recommended to install in the same namespace as Argo CD is running in (argocd by default). For existing installations, which are running in a dedicated namespace.
To retain previous behaviour, set applications_api: argocd in argocd-image-updater-config ConfigMap before updating. However, it is recommended to move your installation into the argocd namespace (or wherever your Argo CD is installed to)
The permissions for the argocd-image-updater-sa ServiceAccount have been adapted to allow read access to resources of type Secret and argoproj.io/Application
This release mainly improves compatibility with different registries and introduces support for rate limiting requests to the registry APIs. Also, Arg
This release mainly improves compatibility with different registries and introduces support for rate limiting requests to the registry APIs. Also, Argo CD Image Updater will now fetch metadata for tags in parallel, instead of doing it sequentially, which greatly improves performance.
A new method for fetching credentials has been added, ext, which allows to execute a script that generates the credentials. Also, credentials configured at the registry level can be set to expire now, to support generated tokens with a limited lifetime.
A new command has been added to argocd-image-updater CLI, namely the test command. This new command allows you to check how Argo CD Image Updater would behave with a certain set of configuration, without having to annotate any live resources in your clusters. For more information on how to use it, see the documentation. It's not feature complete yet, and more features will be added in the future.
Attention: For the latest update-strategy, argocd-image-updater now fetches v2 manifests by default, instead of the v1 manifests in previous versions. This is to improve compatibility with registry APIs, but may result in a significant higher number of manifest pulls. Due to the recent pull limits imposed by Docker Hub, it is not recommended to use latest updated strategy with Docker Hub registry anymore if those pull limits are enforced on your account and/or images, especially if you have more than a couple of tags in your image's repository. Fetching meta data for any given tag counts as two pulls from the view point of Docker Hub.
The default rate limit for API requests is 20 requests per second per registry. If this is too much for your registry, please lower this value in the registries.conf by setting ratelimit to a lower value.
Deprecation notice: The annotation argocd-image-updater.argoproj/ .tag-match has been deprecated in favour of argocd-image-updater.argoproj/ .allow-ta…
This release adds out-of-the-box support for the new GitHub Container Registry ghcr.io and lets users ignore certain tags from a repository.
Also, it adds some usability features & fixes.
Deprecation notice: The annotation argocd-image-updater.argoproj/<image>.tag-match has been deprecated in favour of argocd-image-updater.argoproj/<image>.allow-tags to be consistent with the new argocd-image-updater.argoproj/<image>.ignore-tags annotation. The old annotation will still work, but a warning message will be issued in the log. Users are encouraged to rename their annotations asap, as the tag-match annotation is subject to removal in a future version of the image updater.
Bug fix release for the 0.6 release branch, which fixes several problems accessing custom registries
Bug fix release for the 0.6 release branch, which fixes several problems accessing custom registries
N/A
N/A
Bug fix release for the 0.6 release branch.
Bug fix release for the 0.6 release branch.
N/A
N/A
N/A
This is mainly a bug fix release. It is now possible to skip TLS certificate verification when using self-hosted container registries.
This is mainly a bug fix release. It is now possible to skip TLS certificate verification when using self-hosted container registries.
N/A
Correctly parse version constraints containing equal signs
N/A
N/A
N/A
This release brings mainly bug fixes and other enhancements. The most obvious changes are:
This release brings mainly bug fixes and other enhancements. The most obvious changes are:
latestargocd-image-updater now comes with default RBAC rules for the service account, to enable reading of secrets from the namespace the pod is running in. It is advised to install the updated manifests.
If you use the latest or name update strategy and relied on the semantic
version constraint to limit the list of tags to consider, you will need to
use an additional tag-match annotation to limit the tags. The constraint
will only be used for update strategy semver from v0.5.0 onwards.
This release brings several new features as well as bug fixes.
This release brings several new features as well as bug fixes.
The major new features in this release are the ability to specify per-image pull secrets via an annotation, i.e. argocd-image-updater.argoproj.io/myimage.pull-secret: secret:mynamespace/mysecret#somefield and the pre-filtering of tags returned by the registry. The latter feature allows you to exclude specific tags from being considered for update.
Also, GitHub Docker Registry is now supported.
N/A
One column per quarter.