[Hotfix] Revert dominikh/staticcheck-action from 1.3.1 to 1.3.0 to address failures #1490
Conversation
This file contains 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
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.
Resolves Static Check action failing since 1.3.1 upgrade
Description
Dependabot created pull request that bumped dominikh/staticcheck-action from 1.3.0 to 1.3.1. Since the version was only incremented by a single patch value, we decided to approve the PR and merge it to
main, assuming that there would be no breaking changes and that the Parse Checks action would continue to work and succeed as expected.However, this update broke the Parser Checks action and the checks have consistently failed since this PR was merged. As such, we are going to revert the action version back to 1.3.0 to get the Parser Check actions working again.
This pull request changes:
Steps to manually verify this change:
main