fix(renovate): drop followTag on retired v1 floating tag

[williaby]

Removes followTag: "v1" from the org-workflow Renovate rule. The org tag-protection ruleset forbids re-pointing v* tags, so v1 froze at the v1.1.0 commit and the followed tag silently froze all org-workflow SHA-pin updates. Plain semver tracking of the immutable vX.Y.Z release tags restores update delivery.

Companion to ByronWilliamsCPA/.github#244 (v1 tag retirement) and ByronWilliamsCPA/.claude#251 (CI-057 inversion). Satisfies the inverted CI-057.

Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated automated dependency update configuration to target immutable semantic-version release tags.
  • Stopped following the floating v1 tag for reusable workflows.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Team

Run ID: 4aea7443-69f6-4a82-97a4-975a71fadb04

📥 Commits

Reviewing files that changed from the base of the PR and between adf7083 and 278378a.

📒 Files selected for processing (1)

• renovate.json

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The Renovate configuration now advances reusable-workflow SHA pins from immutable semver release tags instead of following the floating v1 tag.

Changes

Workflow tag tracking

Layer / File(s)	Summary
Update Renovate workflow rule renovate.json	The GitHub Actions Renovate rule now uses immutable semver release tags and removes followTag: "v1".

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 67746

Reusable-workflow SHA updates will track immutable semver release tags rather than the stale floating v1 tag. The configuration change is ready to merge.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the main change: removing the Renovate followTag configuration for the retired floating v1 tag.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch claude/retire-followtag-v1-0

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

This PR updates the repository’s Renovate configuration so GitHub Actions reusable-workflow SHA pins continue to receive updates now that the org’s floating v1 tag is retired/frozen by tag-protection.

Changes:

• Remove followTag: "v1" from the github-actions package rule for ByronWilliamsCPA/.github.
• Update the rule description to document why followTag is intentionally not used and why semver release tags are expected.