Repository navigation
chore: migrate HawkEye to v7 - #62
Merged
geoffreyclaude merged 3 commits intoSep 4, 2026
Merged
Conversation
geoffreyclaude
approved these changes
Sep 4, 2026
geoffreyclaude
left a comment
geoffreyclaude
left a comment
Collaborator
There was a problem hiding this comment.
HawkEye is pinned to 7.0.1, the v7 configuration migration is correct, and both CI jobs pass.
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
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.
Which issue does this PR close?
N/A — this is a maintenance migration for the license-header tooling.
Rationale for this change
The existing HawkEye version and configuration target v6 and are incompatible with the latest v7 release.
What changes are included in this PR?
Are these changes tested?
Yes. HawkEye v7.0.1 validates 42 files with 0 changes, 0 conflicts, and 0 unsupported files. Changed YAML and TOML files also pass syntax validation.
Are there any user-facing changes?
No.