Update Terraform github to v6.7.5

[renovate]

This PR contains the following updates:

Package	Type	Change
github (source)	required_provider	6.7.1 -> 6.7.5

---

Release Notes

integrations/terraform-provider-github (github)

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

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

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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

[github-actions]

GitLab Pipeline Action

General information

Link to pipeline: https://gitlab.com/code0-tech/infrastructure/mensa/-/pipelines/2147115299

Status: Passed
Duration: 1 minutes

Job summaries

tf-plan:server_administration

No changes. Your infrastructure matches the configuration.

tf-plan:github

No changes. Your infrastructure matches the configuration.

tf-plan:main

No changes. Your infrastructure matches the configuration.