Only run broker tests on latest Go #235
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
Current unit test workflows are broken because a dependency of the broker forces a bump to "toolchain go1.21.x" when we use go1.21 in CI. CI automatically bumps the Go toolchain in on-demand-service-broker-release to the latest so we definitely want to test with the latest Go version, but we do not necessarily need to support previous Go toolchains.
|
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/186115119 The labels on this github issue will be updated when the story is started. |
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.
Current unit test workflows are broken because a dependency of the broker forces a bump to "toolchain go1.21.x" when we use go1.21 in CI.
CI automatically bumps the Go toolchain in
on-demand-service-broker-release to the latest so we definitely want to test with the latest Go version, but we do not necessarily need to support previous Go toolchains.