mittwald / mittwald/deploy-container-action
@v1 cannot be resolved because no v1 tag/branch exists
@Hermsi1337 is already working on this.
Since Aug 19, 2025.
- Dominant language
- Go
- Stars
- 10
- Forks
- 2
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 7
Description
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
-
In a GitHub Actions workflow, add:
- uses: mittwald/deploy-container-action@v1 -
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.