Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Automatically detect Go version in the pipeline #210

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mbevc1
Copy link
Contributor

@mbevc1 mbevc1 commented Nov 28, 2023

Issue #, if available: n/a

Description of changes:
Pipelines will automatically use Go version based on go.mod

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@mbevc1 mbevc1 requested a review from a team as a code owner November 28, 2023 18:35
with:
go-version: 'stable'
go-version-file: 'go.mod'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This means we'll need to update go.mod at release to ensure we don't release using Go with a CVE though, right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have check-latest: true so it will only be used to bump minor release, which we'll probably do via go.mod, I assume 🤔

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think I'd prefer to keep using 'stable' as it automatically uses the latest stable go whenever a release is made. I don't trust myself to update go.mod as frequently 😆

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure, I just think it's a nice mechanism testing what the codebase is set to run with, but there could be value in having it future tested too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants