ci: use go version from provider to update workflows #1399
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
rquitales
added
the
impact/no-changelog-required
t0yv0
approved these changes
Feb 20, 2025
rquitales
force-pushed
the
rquitales/use-provider-go-version
branch
from
8b9e23a to
bba88f9
Compare
rquitales
force-pushed
the
rquitales/use-provider-go-version
branch
from
bba88f9 to
bd4d85e
Compare
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.
Proposed Changes
This PR updates the update-workflows workflow to ensure we use a Golang version compatible with the respective provider for updating its own workflows. It achieves this by first checking out the targeted provider repository and extracting the Golang version specified in its
.ci-mgmt.yamlconfig file. If no version is specified, the workflow defaults to the latest "stable" Go release.This change is necessary because our providers use different Go versions, and mismatches can lead to build failures due to incompatible toolchain versions.
Manual testing was conducted by dispatching the workflow against repositories with and without a defined Go version in their config:
Relevant Issues (optional)
Closes #1382.