# Argo v3.0.23

2026-01-22 · [Original release notes](https://github.com/argoproj/argo-cd/releases/tag/v3.0.23) · [Full summary](https://ratatosk.io/en/releases/argo/v3.0.23)

Important fixes 1 · Other changes 2

## Check before upgrading

### Known issues

- **Argo v3.0 reaches end of life**: The v3.0 series reached end of life on 02 Feb 2026 and will receive no further bug fixes or security updates. Supported versions are v3.1 or higher.
  > > [!IMPORTANT]
  > > **END OF LIFE NOTICE**
  > > This is the final release of the `v3.0` release series. As of 02 Feb 2026, this version has reached end of life and will no longer receive bug fixes or security updates.
  > > **Action Required**: Please upgrade to a [supported version](https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/) (v3.1 or higher).

### Upgrade guide

- **Minor-version upgrade guidance**
  > If upgrading from a different minor version, be sure to read the [upgrading](https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/overview/) documentation.

## Important fixes (1)

### Source hydration refresh paths now resolve against `drySource`

- Affects: source-hydrated applications using `argocd.argoproj.io/manifest-generate-paths` with relative paths

Previously, relative annotation paths were expanded against the application's sources, so they did not properly trigger hydration refreshes. Refreshes can now be triggered for those paths, including through webhook handling.

> * 5f9dc64088a9d51423556890883adee73ed7bb5d: fix: cherry pick #25516 to release-3.0 (#26107) (@FourFifthsCode)

## Other changes (2)

- Source Hydrator revision rows now require available SHAs
- Repo-server `/healthz` failure logs clarified

---

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.
