Closed hashicorp-tsccr[bot] closed 12 months ago
Bumping GitHub Actions version to latest TSCCR release.
.github/workflows/depscheck.yaml
actions/checkout
v3.5.3
v4.1.1
.github/workflows/docs-lint.yaml
.github/workflows/gencheck.yaml
.github/workflows/golint.yaml
golangci/golangci-lint-action
v3.6.0
v3.7.0
.github/workflows/issue-opened.yaml
github/issue-labeler
v3.2
v3.3
.github/workflows/lock.yml
dessant/lock-threads
v4.0.1
v5.0.1
.github/workflows/release.yml
actions/upload-artifact
v3.1.2
v3.1.3
.github/workflows/tflint.yaml
.github/workflows/thirty-two-bit.yaml
.github/workflows/unit-test.yaml
This PR was auto-generated by security-tsccr/actions/runs/7082689010
You can alter the configuration of this automation via the hcl config in security-tsccr/automation
Please reach out to #team-prodsec if you have any questions.
Bumping GitHub Actions version to latest TSCCR release.
.github/workflows/depscheck.yaml
actions/checkout
fromv3.5.3
tov4.1.1
(release notes).github/workflows/docs-lint.yaml
actions/checkout
fromv3.5.3
tov4.1.1
(release notes).github/workflows/gencheck.yaml
actions/checkout
fromv3.5.3
tov4.1.1
(release notes).github/workflows/golint.yaml
actions/checkout
fromv3.5.3
tov4.1.1
(release notes)golangci/golangci-lint-action
fromv3.6.0
tov3.7.0
(release notes).github/workflows/issue-opened.yaml
actions/checkout
fromv3.5.3
tov4.1.1
(release notes)github/issue-labeler
fromv3.2
tov3.3
(release notes).github/workflows/lock.yml
dessant/lock-threads
fromv4.0.1
tov5.0.1
(release notes).github/workflows/release.yml
actions/checkout
fromv3.5.3
tov4.1.1
(release notes)actions/checkout
fromv3.5.3
tov4.1.1
(release notes)actions/upload-artifact
fromv3.1.2
tov3.1.3
(release notes).github/workflows/tflint.yaml
actions/checkout
fromv3.5.3
tov4.1.1
(release notes).github/workflows/thirty-two-bit.yaml
actions/checkout
fromv3.5.3
tov4.1.1
(release notes).github/workflows/unit-test.yaml
actions/checkout
fromv3.5.3
tov4.1.1
(release notes)This PR was auto-generated by security-tsccr/actions/runs/7082689010
You can alter the configuration of this automation via the hcl config in security-tsccr/automation
Please reach out to #team-prodsec if you have any questions.