fix release when timestamped tag is used

[monotek]

Type of Change

• Bugfix
• Enhancement / new feature
• Refactoring
• Documentation

Description

• fix release when timestamped tag is used
• see: https://github.com/Staffbase/flux-ai-bridge/actions/runs/27019588358/job/79744482305

Checklist

• Write tests
• Make sure all tests pass
• Update documentation
• Review the Contributing Guideline and sign CLA
• Reference relevant issue(s) and close them after merging

[Copilot]

Pull request overview

This PR fixes release retagging when docker-tag-timestamp is enabled by ensuring a stable <prefix>-<short-sha> tag is still pushed alongside the timestamped branch tag, so the release retag step can find the source image by commit SHA.

Changes:

• Update tag generation to emit an additional legacy <prefix>-<short-sha> alias tag in tag_list when timestamped tags are enabled.
• Add Bats tests to validate tag_list includes (or does not include) the alias tag depending on the timestamp flag.
• Document the additional alias tag behavior in the README (Flux ignores it via the filter pattern).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
scripts/generate-tags.sh	Adds ALIAS_TAG and appends it to TAG_LIST when timestamped tags are enabled, preserving the release retag lookup tag.
tests/generate-tags.bats	Adds coverage for the new alias tag behavior in tag_list for timestamped vs non-timestamped branch tags.
README.md	Documents that timestamp mode also pushes the legacy <prefix>-<short-sha> tag and explains why Flux ignores it.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.