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.
This PR contains the following updates:
6.6.0->6.9.01.13.3->1.14.2~> 1.13.0->~> 1.14.0Release Notes
integrations/terraform-provider-github (github)
v6.9.0Compare Source
What's Changed
🚀 New Features
🐛 Bugfixes
forktoTypeStringand add conditional ForceNew by @diofeher in #2959🪦 Deprecations
🛠️ Maintenance
New Contributors
Full Changelog: integrations/terraform-provider-github@v6.8.0...v6.9.0
v6.8.3Compare Source
Updates how we handle secrets to address provider config and initialization issues (ref: #2903)
Full Changelog: integrations/terraform-provider-github@v6.8.2...v6.8.3
v6.8.2Compare Source
This merge brings the following enhancements from v6.7.5:
Full Changelog: integrations/terraform-provider-github@v6.8.1...v6.8.2
v6.8.1Compare Source
fix: max_file_size was declared as an int but being cast as a float
fix: restricted_file_extensions was panicing due to a Set type mismatch
Full Changelog: integrations/terraform-provider-github@v6.8.0...v6.8.1
v6.8.0Compare Source
What's Changed
🚀 New Features
🐛 Bugfixes
🛠️ Maintenance
📝 Documentation
New Contributors
Full Changelog: integrations/terraform-provider-github@v6.7.0...v6.8.0
v6.7.5Compare Source
[fix]: v6.7.4 causes Internal validation error during TF Init #2855
Full Changelog: integrations/terraform-provider-github@v6.7.4...v6.7.5
v6.7.4Compare Source
v6.7.4
This patch appropriately handles the cases when a Terraform resource has an Update function defined (which was recently added), the Terraform SDK requires that any field that can change must either have
ForceNew: true(meaning changes require resource recreation) or for that field to be a computed-only field.The
destroy_on_driftfield is a provider config setting that controls how drift detection works - it's not a field that maps to the GitHub API. When implementations try to change this field Terraform will execute the plan properly but fail on the apply because the Update function didn't know how to handle the destroy_on_drift change.Lastly reads now handle setting
encrypted_valueandplaintext_valueto nil to trigger an update when the "stored" update dates do not match.Full Changelog: integrations/terraform-provider-github@v6.7.3...v6.7.4
v6.7.3Compare Source
v6.7.3
This patch addresses the issue where the Update function was missed during the cherry pick for
github_actions_secretresource.Tests were also added to avoid regressions in the future.
Full Changelog: integrations/terraform-provider-github@v6.7.2...v6.7.3
v6.7.2Compare Source
v6.7.2
Note: This patch contains the addition of the
destroy_on_driftproperty togithub_actions_secretresource because the exact same issue was present there as well.Bug Fixes
Fixed drift detection bug that caused "Provider produced inconsistent result" errors in github_actions_organization_secret and github_actions_secret resources. The bug occurred when secrets were modified externally - the timestamp wasn't being updated after drift detection, causing infinite loops of false positive drift detection. | #2832
Features
Added destroy_on_drift property to github_actions_secret resource (repository-level secrets), and matches the functionality already available in github_actions_organization_secret. Also includes proper schema migration from v0 to v1 and ensures the property defaults to true for backward compatibility. | #2832
Full Changelog: integrations/terraform-provider-github@v6.7.1...v6.7.2
v6.7.1Compare Source
v6.7.1
Bug Fixes
destroy_on_driftfield to fix regression from v6.7.0 (#2820)This patch release fixes a regression introduced in v6.7.0 where existing
github_actions_organization_secretresources would show invalid state for the newdestroy_on_driftfield.The fix adds a schema migration that automatically sets
destroy_on_drift=truefor existing resources that don't have this field, preventing the need for manual state fixes.Fixes: #2804
Full Changelog: integrations/terraform-provider-github@v6.7.0...v6.7.1
v6.7.0Compare Source
What's Changed
🚀 New Features
github_actions_organization_secret_repositoryresource by @ylascombe in #2760DeployKeyactor type in repository and organization rulesets by @tiulpin in #2748🐛 Bugfixes
🛠️ Maintenance
📝 Documentation
New Contributors
Full Changelog: integrations/terraform-provider-github@v6.6.0...v6.7.0
hashicorp/terraform (hashicorp/terraform)
v1.14.2Compare Source
v1.14.1Compare Source
1.14.1 (December 3, 2025)
BUG FIXES:
test: allow ephemeral outputs in root modules (#37813)
Combinations of replace_triggered_by and -replace could result in some instances not being replaced (#37833)
providers lock: include providers required by terraform test (#37851)
Set state information in the proto request for the
GenerateResourceConfigRPC (#37896)actions: make after_create & after_update actions run after the resource has applied (#37936)
v1.14.0Compare Source
1.14.0 (November 19, 2025)
NEW FEATURES:
List Resources: List resources can be defined in
*.tfquery.hclfiles and allow querying and filterting existing infrastructure.A new Terraform command
terraform query: Executes list operations against existing infrastructure and displays the results. The command can optionally generate configuration for importing results into Terraform.A new GenerateResourceConfiguration RPC allows providers to create more precise configuration values during import. (#37515)
New top-level Actions block: Actions are provider defined and meant to codify use cases outside the normal CRUD model in your Terraform configuration. Providers can define Actions like
aws_lambda_invokeoraws_cloudfront_create_invalidationthat do something imparative outside of Terraforms normal CRUD model. You can configure such a side-effect with an action block and have actions triggered through the lifecycle of a resource or through passing the-invokeCLI flag. (#37553)ENHANCEMENTS:
terraform test: expected diagnostics will be included in test output when running in verbose mode" (#37362)
terraform test: ignore prevent_destroy attribute during when cleaning up tests" (#37364)
terraform stackscommand support for-helpflag (#37645)query: support offline validation of query files via -query flag in the validate command (#37671)
Updates to support the AWS European Sovereign Cloud (#37721)
BUG FIXES:
Retrieve all workspace variables while doing a
terraform import, include variables inherited from variable sets but not overwritten by the workspace. (#37241)Fix OSS backend proxy support by adding a proxy layer for OSS backend operations. Resolves #36897. (#36897)
console and test: return explicit diagnostics when referencing resources that were not included in the most recent operation. (#37663)
query: generate unique resource identifiers for results of expanded list resources (#37681)
The CLI now summarizes the number of actions invoked during
terraform apply, matching the plan output. (#37689)Allow filesystem functions to return inconsistent results when evaluated within provider configuration (#37854)
query: improve error handling for missing identity schemas (#37863)
UPGRADE NOTES:
The parallelism of Terraform operations within container runtimes may be reduced depending on the CPU bandwidth limit setting. (#37436)
Building Terraform 1.14 requires macOS Monterey or later (due to being built on Go 1.25 which imposes these requirements) (#37436)
Previous Releases
For information on prior major and minor releases, refer to their changelogs:
v1.13.5Compare Source
1.13.5 (November 5, 2025)
BUG FIXES:
impure functions could cause templatefile to incorrectly fail consistency checks (#37807)
Allow filesystem functions to return inconsistent results when evaluated within provider configuration (#37854)
v1.13.4Compare Source
1.13.4 (October 15, 2025)
BUG FIXES:
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.