chore(deps): bump mathieudutour/github-tag-action from 6.2 to 7

[dependabot]

Bumps mathieudutour/github-tag-action from 6.2 to 7.

Changelog

Sourced from mathieudutour/github-tag-action's changelog.

v7 upgrades the action to Node 24 and introduces breaking changes to version calculation and branch handling. Review the migration guide before upgrading from v6.

• Run on Node 24 and ship a self-contained dist/ bundle with both supported commit presets, templates, dependencies, and license notices. Refresh the lockfile, remove the old Octokit dependency chain, and retain proxy support.
• Align analysis and changelogs on Conventional Commits, including feat!. Angular remains selectable.
• Match whole branch names; an empty prerelease list now means no prerelease branches. Never publish from PR events or recursively process tag events. Preview versions include a commit SHA suffix.
• Fetch all tags and all compare-commit pages. Explicitly restricted tag fetching fails when results might be incomplete. Read initial commit history instead of comparing against a fabricated HEAD baseline.
• Skip version creation when no eligible commits remain, unless custom or forced versioning was explicitly requested.
• Keep stable release baselines separate from unrelated prereleases; match prerelease identifiers exactly, honor the first prerelease default, increment existing RCs, and allow higher-level changes to advance the RC base.
• Add path/scope/ignore filters, opt-in squash-bullet parsing, tag-stream filtering, explicit bump/version inputs, local/moving/rolling tags, repository/ref/directory overrides, and release metadata outputs.
• Retry transient API reads and fall back to complete local Git history for compare failures. No history means no guessed release. Optional soft failure clears release outputs.

Migration

See Migrating from v6 to v7 for changed defaults, workflow examples, prerelease behavior, and a dry-run validation procedure.

New inputs are opt-in unless explicitly described above and require v7. See the README for the full input contract.

Commits

• af99e60 fix CI on windows
• 8e15535 version 7
• 9d35d64 Bump ws from 7.5.5 to 7.5.10 (#216)
• 17d01dc Bump braces from 3.0.2 to 3.0.3 (#215)
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[rhacs-bot]

A single node development cluster (infra-pr-1918) was allocated in production infra for this PR.

CI will attempt to deploy quay.io/rhacs-eng/infra-server: to it.

🔌 You can connect to this cluster with:

gcloud container clusters get-credentials infra-pr-1918 --zone us-central1-a --project acs-team-temp-dev

🛠️ And pull infractl from the deployed dev infra-server with:

nohup kubectl -n infra port-forward svc/infra-server-service 8443:8443 &
make pull-infractl-from-dev-server

🔓 You must go to to export an . Your token from the prod infra instance will not work with dev environments.

🚲 You can then use the dev infra instance e.g.:

bin/infractl -k -e localhost:8443 whoami

⚠️ Any clusters that you start using your dev infra instance should have a lifespan shorter then the development cluster instance. Otherwise they will not be destroyed when the dev infra instance ceases to exist when the development cluster is deleted. ⚠️

Further Development

☕ If you make changes, you can commit and push and CI will take care of updating the development cluster.

🚀 If you only modify configuration (chart/infra-server/configuration) or templates (chart/infra-server/{static,templates}), you can get a faster update with:

make helm-deploy

Logs

Logs for the development infra depending on your @redhat.com authuser:

• authuser=0
• authuser=1
• authuser=2

Or:

kubectl -n infra logs -l app=infra-server --tail=1 -f