Currently rubykatzen/docker-apps only publishes exact patch tags on release (e.g. v0.2.2). Since rubykatzen/releaser >= v0.5.3 publishes floating major/minor tags automatically on release, updating to it would add v0 and v0.2 floating tags.
This would allow downstream repos to pin to @v0.2 instead of @v0.2.2, staying on the latest patch automatically.
Context
dupmachine/docker-apps-extra references rubykatzen/docker-apps/.github/actions/build-bundle in its release workflow. We tried pinning to @v0.2 but it failed because the floating tag doesn't exist yet.
🤖 Generated with Claude Code
Currently
rubykatzen/docker-appsonly publishes exact patch tags on release (e.g.v0.2.2). Sincerubykatzen/releaser>= v0.5.3 publishes floating major/minor tags automatically on release, updating to it would addv0andv0.2floating tags.This would allow downstream repos to pin to
@v0.2instead of@v0.2.2, staying on the latest patch automatically.Context
dupmachine/docker-apps-extrareferencesrubykatzen/docker-apps/.github/actions/build-bundlein its release workflow. We tried pinning to@v0.2but it failed because the floating tag doesn't exist yet.🤖 Generated with Claude Code