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

fix(ci): use go version of go.mod #1858

Merged
merged 1 commit into from
Feb 28, 2024
Merged

fix(ci): use go version of go.mod #1858

merged 1 commit into from
Feb 28, 2024

Conversation

MaineK00n
Copy link
Collaborator

@MaineK00n MaineK00n commented Feb 28, 2024

What did you implement:

install go version of go.mod

2024/02/28 05:28:21 Autobuilder was built with go1.21.7, environment has go1.20.14
2024/02/28 05:28:21 LGTM_SRC is /home/runner/work/vuls/vuls
2024/02/28 05:28:21 Found go.mod, enabling go modules
2024/02/28 05:28:21 The go.mod file requires version v1.21 of Go, but version v1.20.14 is installed. Consider adding an actions/setup-go step to your workflow.
go: go.mod file indicates go 1.21, but maximum version supported by tidy is 1.20

/~https://github.com/future-architect/vuls/actions/runs/8075744361/job/22063101584?pr=1856

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

2024/02/28 07:07:58 Autobuilder was built with go1.21.7, environment has go1.21.7

/~https://github.com/future-architect/vuls/actions/runs/8076575378/job/22065274478?pr=1858

Checklist:

You don't have to satisfy all of the following.

  • Write tests
  • Write documentation
  • Check that there aren't other open pull requests for the same issue/feature
  • Format your source code by make fmt
  • Pass the test by make test
  • Provide verification config / commands
  • Enable "Allow edits from maintainers" for this PR
  • Update the messages below

Is this ready for review?: YES

Reference

@MaineK00n MaineK00n self-assigned this Feb 28, 2024
@MaineK00n MaineK00n merged commit 05e0f05 into master Feb 28, 2024
4 checks passed
@MaineK00n MaineK00n deleted the MaineK00n/fix-codeql branch February 28, 2024 07:20
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.

1 participant