fix: change release-doc-sync default meta-repo-ref to v1#43
Merged
TMHSDigital merged 1 commit intomainfrom Apr 26, 2026
Merged
Conversation
The previous default of v1.0 referenced a tag that was never created. release.yml auto-maintains v1 (floating major) and v1.MINOR tags but never created a v1.0 lightweight tag. First-time consumers of release-doc-sync@v1 calling the action without an explicit override hit a tag resolution failure at checkout. Surfaced during Blender-Developer-Tools v0.1.0 release pipeline. The workaround in that repo (commit 98e9a57) sets meta-repo-ref: v1.9.1 explicitly. With this default change, future first-time consumers will work without that workaround. The input description string is updated in the same change to match the new default. Tracks DTD#42. Closes #42 Made-with: Cursor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
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
1 participant
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.
Summary: change the default value of release-doc-sync@v1 action input
meta-repo-reffromv1.0tov1.Background
release-doc-syncchecks out the meta-repo at the ref provided bymeta-repo-ref. The previous defaultv1.0was never created.release.ymlauto-maintainsv1(floating major) andv1.MINOR(e.g.,v1.9), but nov1.0lightweight tag exists in the repo. New consumers calling the action without overridingmeta-repo-reffailed at the action's internalactions/checkout@v5step withgit fetch ... refs/tags/v1.0*returning empty and exit code 1.Fix
Change the input default from
v1.0tov1(the floating major).v1is auto-maintained on every release.The input description is updated in the same change so the docstring matches the new default.
Impact
release-doc-sync@v1work without passingmeta-repo-refexplicitly.v1.9.1, others using explicit@v1.Xpins) are unaffected.@v1and@v1.9floating tags. Behavior under those tags will pick up this fix automatically when the post-merge auto-release fires.Surfaced by
Blender-Developer-Tools v0.1.0 release run, where the action failed at checkout and was unblocked by setting
meta-repo-ref: v1.9.1explicitly (Blender commit98e9a57). With this change, that workaround is no longer required for future first-time consumers.Closes #42.