Scope go-git minimumReleaseAge to pseudo-version updates only

[Copilot]

The current go-git Renovate rule applies a 7-day minimumReleaseAge to all updates, which also delays cut releases. This change limits that delay to pseudo-version bumps (new commits on main) while leaving tagged releases unblocked.

• Rule split for go-git dependencies

  • Kept the existing go-git grouping rule (gomod + package prefixes) for update grouping behavior.
  • Removed minimumReleaseAge from that base grouping rule.

• Pseudo-version-only age gating

  • Added a second gomod package rule for the same go-git prefixes.
  • Applied minimumReleaseAge: "7 days" only when matchNewValue matches Go pseudo-version format (YYYYMMDDHHMMSS-<12hex>[+incompatible]).

{
  "matchManagers": ["gomod"],
  "matchPackagePrefixes": [
    "github.com/go-git/",
    "github.com/pjbgf/sha1cd"
  ],
  "matchNewValue": "/\\d{14}-[0-9a-f]{12}(\\+incompatible)?$/",
  "minimumReleaseAge": "7 days"
}

[Copilot]

Pull request overview

Updates the shared Renovate configuration to stop delaying tagged go-git releases while still applying a 7-day aging window to go pseudo-version updates (i.e., new commits on the default branch).

Changes:

• Split the existing go-git gomod package rule so the grouping rule no longer applies minimumReleaseAge.
• Added a second gomod rule for the same go-git prefixes that applies minimumReleaseAge: "7 days" only when the new version matches a Go pseudo-version suffix via matchNewValue.

---

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