GHA to prompt reviewers to think about dependency changes when backporting #37800
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
SarahFrench
added
the
no-changelog-needed
Member
Author
|
Here's the check running on this PR: https://github.com/hashicorp/terraform/actions/runs/18715567800/job/53374010319?pr=37800 |
mildwonkey
approved these changes
Oct 22, 2025
Contributor
mildwonkey
left a comment
mildwonkey
left a comment
There was a problem hiding this comment.
Nice, this should help!
Member
Author
|
Thanks! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 GHA posts comments to PRs if a dependency change is going to be backported to a release branch.
If a PR has diffs detected in go.mod files (root and nested locations) and the PR has a label containing "backport" then this message will be posted to the PR:
The comment will be removed if the PR is updated to:
This automation is a way to deal with lack of fully-automated Mend scanning, see #37584
Target Release
N/A
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry