-
Notifications
You must be signed in to change notification settings - Fork 56
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
Update code owners and GH actions #90
Conversation
stevendpclark
commented
May 10, 2024
- Update the code owners file as the cryptosec team apparently owns this now
- Swap the Jira sync workflow to use the hashicorp/vault-workflows-common workflow to get rid of node 16 deprecation warnings
- Update the workflows using the deprecated set-output command to the new environment style based on https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
- Update pinned actions to the latest supported by the TSCCR tool.
- Update the various workflows to get rid of the set-output commands and use the new way using environment files based on the following blog post. https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
@@ -1 +1 @@ | |||
# release configuration | |||
* @hashicorp/vault-crypto |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Working with Luciano on getting the vault-crypto group write access to the repo.
.github/workflows/build.yml
Outdated
|
||
- name: Setup go | ||
uses: actions/setup-go@93397bea11091df50f3d7e59dc26a7711a8bcfbe # v4.1.0 | ||
uses: actions/setup-go@cdcb36043654635271a94b9a6d1392de5bb323a7 # v5.0.1 | ||
with: | ||
go-version: ${{ needs.get-go-version.outputs.go-version }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd suggest removing the get-go-version job and just use .go-version
here, since setup-go supports that now.
go-version: ${{ needs.get-go-version.outputs.go-version }} | |
go-version-file: .go-version |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
TIL: I thought you could only specify go.mod/go.work files but looking at the source it does seem to accept other files with just the Go version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Addressed in ffda033
- Eliminate the job step to get the Go version manually and leverage setup-go's argument to read it from a repository file instead.