Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Oct 25, 2025

This PR contains the following updates:

Package Type Update Change
github (source) required_provider minor 6.6.0 -> 6.8.3

Release Notes

integrations/terraform-provider-github (github)

v6.8.3

Compare 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.2

Compare Source

⚠️ This release is deprecated, please use v6.8.3 instead

This merge brings the following enhancements from v6.7.5:

  • Added destroy_on_drift field to both github_actions_secret and github_actions_organization_secret
  • Improved drift detection logic with configurable behavior
  • Added schema migrations for backward compatibility
  • Enhanced test coverage for drift detection scenarios
  • Fixed ForceNew field configurations

Full Changelog: integrations/terraform-provider-github@v6.8.1...v6.8.2

v6.8.1

Compare Source

⚠️ This release is deprecated, please use v6.8.2 instead

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.0

Compare Source

What's Changed

🚀 New Features
  • fix/feature: Adds support for max_file_size, max_file_path_length, file_extension_restriction, and unknown rulesets for repos and orgs by @​nickfloyd in #​2821
  • feat: Handle error management on resources when dealing with archived repos. by @​nickfloyd in #​2837
  • feat: Update removal operations for related resources to now gracefully handle deleting archived repositories by @​nickfloyd in #​2844
  • feat: support workflow permissions in repository by @​M0NsTeRRR in #​2309
  • feat: implement missing data source github_actions_environment_public_key by @​nobbs in #​2500
  • feat: Adds migration for destory-on-drift for actions organization secret to prevent state from getting out of sync with the schema by @​nickfloyd in #​2820
  • feat: Adds DiffSuppressFunc and DiffSuppressOnRefresh to resources that have etag properties to suppress etag-related diffs by @​nickfloyd in #​2840
  • feat: Max per page by @​dee-kryvenko in #​2703
  • feat(core): add fork functionality by @​hminaee-tc in #​2678
🐛 Bugfixes
🛠️ Maintenance
📝 Documentation

New Contributors

Full Changelog: integrations/terraform-provider-github@v6.7.0...v6.8.0

v6.7.5

Compare 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.4

Compare Source

v6.7.4

⚠️ This release is deprecated, please use v6.7.5 instead

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_drift field 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_value and plaintext_value to 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.3

Compare Source

v6.7.3

⚠️ This release is deprecated, please use v6.7.5 instead

This patch addresses the issue where the Update function was missed during the cherry pick for github_actions_secret resource.
Tests were also added to avoid regressions in the future.

Full Changelog: integrations/terraform-provider-github@v6.7.2...v6.7.3

v6.7.2

Compare Source

v6.7.2

⚠️ This release is deprecated, please use v6.7.5 instead

Note: This patch contains the addition of the destroy_on_drift property to github_actions_secret resource 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.1

Compare Source

v6.7.1

⚠️ This release is deprecated, please use v6.7.5 instead

Bug Fixes
  • github_actions_organization_secret: Add state migration for destroy_on_drift field to fix regression from v6.7.0 (#​2820)

This patch release fixes a regression introduced in v6.7.0 where existing github_actions_organization_secret resources would show invalid state for the new destroy_on_drift field.

The fix adds a schema migration that automatically sets destroy_on_drift=true for 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.0

Compare Source

What's Changed

🚀 New Features
🐛 Bugfixes
🛠️ Maintenance
📝 Documentation

New Contributors

Full Changelog: integrations/terraform-provider-github@v6.6.0...v6.7.0


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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@digger-cloud
Copy link

digger-cloud bot commented Oct 25, 2025

❌ Error loading digger config: error loading digger.yml: error cloning and loading config could not read the file both digger.yml and digger.yaml are missing: open /tmp/repo1239580936/digger.yaml: no such file or directory

@renovate renovate bot changed the title chore(deps): Update Terraform github to v6.7.0 chore(deps): Update Terraform github to v6.7.5 Nov 1, 2025
@renovate renovate bot force-pushed the renovate/github-6.x branch from 21d7fa0 to 1fa05e4 Compare November 1, 2025 07:40
@digger-cloud
Copy link

digger-cloud bot commented Nov 1, 2025

❌ Error loading digger config: error loading digger.yml: error cloning and loading config could not read the file both digger.yml and digger.yaml are missing: open /tmp/repo1636243391/digger.yaml: no such file or directory

@renovate renovate bot changed the title chore(deps): Update Terraform github to v6.7.5 chore(deps): Update Terraform github to v6.8.2 Nov 15, 2025
@renovate renovate bot force-pushed the renovate/github-6.x branch from 1fa05e4 to f6f25e6 Compare November 15, 2025 08:09
@digger-cloud
Copy link

digger-cloud bot commented Nov 15, 2025

❌ Error loading digger config: error loading digger.yml: error cloning and loading config could not read the file both digger.yml and digger.yaml are missing: open /tmp/repo2412160160/digger.yaml: no such file or directory

@renovate renovate bot changed the title chore(deps): Update Terraform github to v6.8.2 chore(deps): Update Terraform github to v6.8.3 Nov 19, 2025
@renovate renovate bot force-pushed the renovate/github-6.x branch from f6f25e6 to e2a1d98 Compare November 19, 2025 03:47
@digger-cloud
Copy link

digger-cloud bot commented Nov 19, 2025

❌ Error loading digger config: error loading digger.yml: error cloning and loading config could not read the file both digger.yml and digger.yaml are missing: open /tmp/repo2703018063/digger.yaml: no such file or directory

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant