8989 runs-on: ubuntu-latest
9090 steps:
9191 - name: Checkout
92- uses: actions/checkout@v5
92+ uses: actions/checkout@v6
9393
9494 - name: Fail on malformatted files
9595 uses: devops-infra/action-format-hcl@v1.1.0
@@ -109,7 +109,7 @@ jobs:
109109 runs-on: ubuntu-latest
110110 steps:
111111 - name: Checkout
112- uses: actions/checkout@v5
112+ uses: actions/checkout@v6
113113
114114 - name: Format HCL files
115115 uses: devops-infra/action-format-hcl@v1.1.0
@@ -135,7 +135,7 @@ jobs:
135135 format-hcl:
136136 runs-on: ubuntu-latest
137137 steps:
138- - uses: actions/checkout@v5
138+ - uses: actions/checkout@v6
139139
140140 - uses: devops-infra/action-format-hcl@v1.1.0
141141 id: pin-patch
@@ -162,6 +162,29 @@ If you have any questions or need help, please:
162162- 📝 Create an [issue](https://github.com/devops-infra/action-format-hcl/issues)
163163- 🌟 Star this repository if you find it useful!
164164
165+ # # 🧪 End-to-End Validation
166+ Use the manual workflow `.github/workflows/manual-e2e-validate.yml` to validate this action against the centralized E2E repository.
167+
168+ - ` mode=image` validates a published image tag (recommended for `-test` and `-rc` release checks).
169+ - ` mode=ref` validates ref-oriented E2E paths against stable pinned action refs.
170+
171+ CI/CD automation also runs these E2E checks automatically :
172+
173+ - Pull requests : E2E validation runs through reusable org workflows.
174+ - Release branch prepare : E2E validation runs against release candidate artifacts (`-rc`).
175+ - Release create : E2E validation runs against production release artifacts.
176+
177+ Example trigger inputs :
178+
179+ ` ` ` text
180+ mode=ref
181+ ` ` `
182+
183+ ` ` ` text
184+ mode=image
185+ image_tag=v1.2.3-test
186+ ` ` `
187+
165188# # Forking
166189To publish images from a fork, set these variables so Task uses your registry identities :
167190` DOCKER_USERNAME` , `DOCKER_ORG_NAME`, `GITHUB_USERNAME`, `GITHUB_ORG_NAME`.
0 commit comments