build(deps): Bump workflows to latest trusted versions#243
Merged
Conversation
kmoe
approved these changes
Sep 9, 2024
Member
kmoe
left a comment
kmoe
left a comment
There was a problem hiding this comment.
macos-latest fail while building Vault from git rev is a known issue in the nightly and not caused by this change
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Bumping GitHub Actions version to latest TSCCR release.
.github/workflows/build.ymlactions/upload-artifactfromv4.3.6tov4.4.0(release notes)actions/upload-artifactfromv4.3.6tov4.4.0(release notes)actions/upload-artifactfromv4.3.6tov4.4.0(release notes)This PR was auto-generated by security-tsccr/actions/runs/10767488526
You can alter the configuration of this automation via the hcl config in security-tsccr/automation
This PR can be regenerated by dispatching the GitHub workflow Pin Action Refs. Please reach out to #team-prodsec if you have any questions.