chore: bump apidiff.yaml go version #360
Merged
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
Signed-off-by: Carlos Salas <[email protected]>
mjura
approved these changes
Jan 17, 2024
alexander-demicev
approved these changes
Jan 17, 2024
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.
What this PR does / why we need it:
For the last couple of days we've had API diff validation workflow failing on new PRs.
After some investigation, it looks like this matches
joelanford/go-apidiff's new release. As we're using the latest version here, CI is failing because our workflow is configured to use Go 1.18 while this new API diff action requires >=1.19.This PR updates the workflow's Go version to match the project's (Go 1.20).
Which issue(s) this PR fixes
Issue #359
Special notes for your reviewer:
Checklist: