chore(provider): bump integrations/github 6.10.2 -> 6.12.1#63
Merged
Conversation
The terraform-provider-github 6.12 line is several point releases ahead of the 6.10.2 currently pinned. The bump is motivated by the allow_forking provider-default issue: 6.10.2 treats Terraform `null` as the schema default `false`, which causes the provider to always include `allow_forks` in PATCH payloads. PATCH then 422s on personal- account private repositories. 6.12.x's changelog may include nullable handling for allow_forking (needs the next deploy to confirm). If the upgrade resolves the 422, no further code changes are needed and the ownership-aware default landed in #62 will behave as intended. If it doesn't resolve, a follow-up PR adds an explicit `managed: optional(bool, true)` flag to the YAML schema and filters runtime-managed repos accordingly. versions.tf: bump constraint. .terraform.lock.hcl: remove the github provider block so CI's `terraform init` regenerates it for 6.12.1. The aws and time provider blocks are unchanged. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Terraform Framework Test Results
Runs: 54 total, 54 passed, 0 failed, 0 skipped Full test outputCommit: bf2efb3 |
NWarila
added a commit
to NWarila/github-terraform-runner
that referenced
this pull request
May 26, 2026
Tests whether terraform-provider-github 6.12.1 correctly omits `allow_forks` from PATCH payloads when Terraform value is null. See [nwarila-platform/github-terraform-framework#63](nwarila-platform/github-terraform-framework#63). | | Before | After | |---|---|---| | uses: SHA | abda8e1f | 7f2cf0b6 | | framework_ref | abda8e1f | 7f2cf0b6 | If deploy succeeds for the 3 personal-account private repos after this lands, F-A is resolved. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 task
NWarila
added a commit
that referenced
this pull request
May 26, 2026
Adds a status preamble to REVIEW_REMEDIATION_PLAN.md recording per-finding implementation state. 7 of 9 findings now marked Done (Finding 4 closed by this session's PRs #62/#63); 1 REJECTED per existing doc; 1 follow-up tracked (manage_codeowners_files opt-in flag). ## Test plan - [ ] CI green (markdownlint) Local: markdownlint-cli2 → 0 errors. Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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
Bumps `integrations/github` from `6.10.2` to `6.12.1` (3 minor versions). Motivated by the `allow_forking` provider-default behavior: 6.10.2 treats Terraform `null` as the schema default `false`, which causes the provider to always include `allow_forks` in PATCH payloads. PATCH then 422s on personal-account private repositories.
6.12.x may include nullable handling for `allow_forking` (the next deploy will confirm). If the upgrade resolves the 422, no further code changes are needed and the ownership-aware default landed in #62 will behave as intended.
Changes
Test plan
Fallback
If 6.12.1 doesn't fix the 422, follow-up PR adds `managed: optional(bool, true)` to the YAML schema and filters at the locals layer.