Skip to content

fix(renovate): skip the release-age soak for reqstool's own packages - #286

Merged
jimisola merged 2 commits into
mainfrom
fix/renovate-no-soak-for-reqstool
Oct 27, 2026
Merged

jimisola merged 2 commits into
mainfrom
fix/renovate-no-soak-for-reqstool

Conversation

@jimisola

Copy link
Copy Markdown
Member

What & Why

minimumReleaseAge (3 days for minor/patch, 7 for major) exists to catch a bad third-party release before we adopt it. On our own packages it only delays the org. Bundling reqstool 1.0.0 into reqstool-vscode would have waited 7 days as a major, so it was bumped by hand (reqstool-vscode#162).

The new rule sits last in packageRules, because the last match wins, and resets the age for:

Pattern Covers
`/^reqstool([-/] $)/`
/^@reqstool\\// npm @reqstool/*
/^io\\.github\\.reqstool[.:]/ Maven io.github.reqstool:*, the Gradle plugin io.github.reqstool.gradle-plugin

Automerge is unchanged: minor and patch bumps still auto-merge once CI is green, and majors still need a manual merge.

Test plan

  • renovate-config-validator --strict passes locally
  • Next Renovate run opens reqstool bumps without a pending release-age status

minimumReleaseAge exists to catch a bad third-party release before it is
adopted. Applied to our own packages it only delays the org: bundling
reqstool 1.0.0 into reqstool-vscode would have waited 7 days as a major.

Signed-off-by: Jimisola Laursen <jimisola@jimisola.com>
@jimisola jimisola self-assigned this Oct 27, 2026
@jimisola
jimisola merged commit 778ec47 into main Oct 27, 2026
5 checks passed
@jimisola
jimisola deleted the fix/renovate-no-soak-for-reqstool branch October 27, 2026 23:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant