Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔍 Action pin bumped across a major version jump for the reusable workflow
.github/workflows/_checks.yml:57jumps from v5.6.0 straight to v7.0.0, while.github/workflows/python-lint.yml:26came from v6.2.0. Both now share the same pinned SHA, so drift is resolved. The steps only usepython-version: "3.12"(nocache, no outputs consumed), so the major-version input/output changes in v7 are unlikely to affect these jobs. Note that_checks.ymlis a reusable gate documented as mirroring wave-foundation'schecks.yml(see the header comment at.github/workflows/_checks.yml:3-6); if the upstream copy in wave-foundation is not bumped in parallel, the two copies drift, which that comment explicitly warns against.Was this helpful? React with 👍 or 👎 to provide feedback.