provider: bump to 6.11.1-gr.2 for the ruleset validation fix - #76
Merged
Conversation
6.11.1-gr.1 rejects rulesets using update_allows_fetch_and_merge at plan time: a client-side validation treats it as a rule type when it is a parameter of the update rule. gr.2 carries the fix. Once released, restore the parameter to the repos/*.yaml it was removed from and confirm the plan is clean.
dev-milos
marked this pull request as ready for review
August 17, 2026 10:38
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.
Closes G-Research/gr-oss#1429
6.11.1-gr.1cannot plan any ruleset that setsupdate_allows_fetch_and_merge: avalidation added in 6.11.0 walks the keys of the
rulesblock and rejects the name as arule type, when it is a parameter of the
updaterule. Because state is shared, oneaffected repository blocked planning across the whole workspace.
6.11.1-gr.2carries the two-line fix(G-Research-Forks/terraform-provider-github#19, cherry-picked from
integrations/terraform-provider-github#3547 while that awaits review upstream).
Bumps the three tracked pin sites.
backend.tfis a gitignored local artefact and is nottracked.
Follow-up, in the config repo
The parameter was removed from
perfetto.yamlandconsuldotnet.yamlduring testing tounblock planning. With this provider it can be restored; a plan then confirms the fix end to
end. That is the last open item from the release-testing cycle.
Verification
Found and reproduced during release testing against a real organisation, where the parameter
blocked planning. The provider fix was built and the release cut as
v6.11.1-gr.2; theconfig-repo plan re-verification follows once this is on a testable ref.