@v1 cannot be resolved because no v1 tag/branch exists

[geldmacher]

What happened
Using mittwald/deploy-container-action@v1 fails with:

Unable to resolve action `mittwald/deploy-container-action@v1`, unable to find version `v1`

Steps to reproduce

1. In a GitHub Actions workflow, add:

   - uses: mittwald/deploy-container-action@v1

2. Run the workflow.

Expected
@v1 resolves to the latest v1.x release.

Actual
Resolution fails because the repository has patch tags like v1.0.x but no movable v1 tag or branch.

Workarounds

• Pin to an explicit release:

  - uses: mittwald/deploy-container-action@v1.0.x

• Or pin to a commit SHA.

Proposed fix
Create and maintain a moving major tag v1 that points to the latest v1.x release. This matches common Actions versioning practice and lets users safely depend on the major line.

[Hermsi1337]

Good catch, thanks for pointing this out!
You’re totally right — without a moving v1 tag, @v1 just won’t work.

I’ll whip up some GitHub Actions kung-fu 🥷 to keep that tag updated automatically, so @v1 will always point to the latest v1.x release.

Shouldn’t be long until this is sorted 🚀 (I hope, lol)

[martin-helmich]

In the meantime: For the last versions that I've tagged, I also updated and pushed the v1 tag accordingly.

(although this obviously isn't perfect, as one [as a maintainer] needs to remember to manually update that tag as part of their release process)