`latest` tag in auto-mode is applied to older major versions about metadata-action

[crazy-max]

idk, if this is the intended behaviour

This is the expected behavior, see https://github.com/docker/metadata-action#latest-tag

You should have a condition on setting latest only for latest release (v2 in your case). I have this kind of pattern in https://github.com/crazy-max/docker-nextcloud/blob/c9a16f5914faae0f36caaea0290d41cbe8914f37/.github/workflows/build.yml#L56

In your case:

flavor: |
  latest=${{ startsWith(github.ref, 'refs/tags/v2') }}

[douglasparker]

idk, if this is the intended behaviour

This is the expected behavior, see https://github.com/docker/metadata-action#latest-tag

You should have a condition on setting latest only for latest release (v2 in your case). I have this kind of pattern in https://github.com/crazy-max/docker-nextcloud/blob/c9a16f5914faae0f36caaea0290d41cbe8914f37/.github/workflows/build.yml#L56

In your case:

flavor: |
  latest=${{ startsWith(github.ref, 'refs/tags/v2') }}

Is there a better way to handle this?

I was following this issue because I'd like to avoid having to update the workflow for every new major version release.

It would be much better if this action was smarter about the usage of the latest tag.

Why make people go through the extra work? 2 is greater than 1.

Backporting a bug fix should not update the latest tag to an older version...