chore(deps): update actions #68
Open
Conversation
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
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/actions
branch
2 times, most recently
from
1b33d12 to
48ef1d7
Compare
renovate
bot
force-pushed
the
renovate/actions
branch
3 times, most recently
from
97d6917 to
3664db2
Compare
renovate
bot
force-pushed
the
renovate/actions
branch
from
3664db2 to
9349092
Compare
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.
This PR contains the following updates:
6.6.0->6.7.51.13.3->1.13.5Release Notes
integrations/terraform-provider-github (github)
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.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.