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

[coderabbitai]

Warning

Review limit reached

@williaby, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 5f351820-77d9-4878-9331-fbcd6119da00

📥 Commits

Reviewing files that changed from the base of the PR and between ab325a9 and 12be67e.

📒 Files selected for processing (1)

• renovate.json

✨ Finishing Touches

🧪 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.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull request overview

Updates Renovate configuration so reusable workflow SHA pin updates are no longer blocked by a frozen floating v1 tag, restoring normal semver-based update delivery for org workflow dependencies.

Changes:

• Removed followTag: "v1" behavior for org reusable workflow dependencies, switching back to plain semver tracking.
• Added an explicit versioning: "semver" for the org reusable workflow rule.
• Reformatted renovate.json for consistent multi-line arrays and readability.