Discontinue floating-tags-action

[marians]

floating-tag-action is used for creating and updating major version tags like v2 whenever a release like v2.3.1 is made.

The action is used by GitHub action publishers to allow action users to reference only a specific major version of the action, but not a minor or patch version. Example:

uses: acme/myaction@v2

According to the GitHub Actions docs:

If the action publishes major version tags, you should expect to receive critical fixes and security patches while still retaining compatibility. Note that this behavior is at the discretion of the action's author.

actions/checkout@v5 works because there is a v5 tag in that repo.

This practice is actually against our security best practice of pinning a particular actions version by commit SHA. Hence ourselves we don't have a use for floating-tags-actions . It would only be a convenience service to users of our actions outside the company.

See internal discussion

[marians]

We enable the process of ensuring major version tags in giantswarm/github for Team Honeybadger owned repositories only, via the enableFloatingMajorTags property. The repos are:

• floating-tags-action itself
• gitleaks-action
• helm-values-gen
• install-binary-action
• schemalint
• subtree-util

This is then carried through the align-files workflow and action code to devctl into the "Create release" workflow.

We also have a separate reusable workflow https://github.com/giantswarm/github-workflows/blob/main/.github/workflows/ensure-major-version-tags.yaml only for that purpose.

All of this could be cleaned up.

[marians]

Moving this to blocked/waiting for a bit to wait for vetos to https://gigantic.slack.com/archives/C0251MXL5/p1770214379261349

[marians]

No vetos, we'll proceed.