chore(ci): updating ci badge and go version #9
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.
Problem Statement
What is the current behavior? Why and how does it need to change?
The current CI badge needs to be fixed and pointed at the correct CI system.
Description of Change
Please include a summary of the change and, if applicable, tag related issues, add code snippets or logs.
I updated the CI Badge to work from GitHub Actions and bumped the Go version, as 1.16 was no longer viable for CI.
I bumped it to 1.18, the lowest version that can be supported.
Breaking Change
Is this a breaking change?
Yes, moving from Go 1.16 to 1.18.
Caveats
Please list any caveats or special considerations for this change.