ci: track engine-test-data semver tags via Renovate#283
Merged
Conversation
emyller
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
The
git-submodulesmanager defaults toversioning: "git", which treats the.gitmodulesbranch = v3.x.yvalue as an opaque git ref. Renovate only refreshes that tag's (immutable) commit SHA and never proposes a newer tag, so theengine-test-datasubmodule has only ever been bumped manually — it stayed onv3.7.0even afterv3.10.0was released.Fix
Set
versioning: "semver-coerced"on thegit-submodulesmanager so Renovate ranks the semver tags and opens bump PRs (e.g.v3.7.0→v3.10.0).Notes
.gitmodulesalready uses thebranchfield, so no change is needed there. This is a config-only change; the actual version bump will come as a follow-up Renovate PR.