No description
  • JavaScript 100%
Find a file
Ryan Cragun 6ec106c8f8
security: override undici to 6.24.0 to resolve GHSA-v9p9-hfj2-hcw8 (#69)
It appears that our usage of @action/http-client transitively
"depends" (from what I can see, it's not actually used and probably
ought to be a dev dependency in the http-client module) on undici
6.23.0[0]. The upstream hasn't been updated yet so we add an
override for it here. Since we're doing a security release I also
updated all of our outdated deps.

[0]: https://github.com/actions/toolkit/blob/main/packages/http-client/package-lock.json#L235

Signed-off-by: Ryan Cragun <me@ryan.ec>
2026-03-16 10:48:17 -06:00
.github change the codeowners to a more relevant team (#68) 2026-03-03 13:09:29 -07:00
__tests__ [VAULT-39456] upgrade to node 24 (#63) 2025-09-11 10:56:44 -06:00
dist security: override undici to 6.24.0 to resolve GHSA-v9p9-hfj2-hcw8 (#69) 2026-03-16 10:48:17 -06:00
src security: override undici to 6.24.0 to resolve GHSA-v9p9-hfj2-hcw8 (#69) 2026-03-16 10:48:17 -06:00
.copywrite.hcl copywrite: add copywrite headers support (#51) 2024-04-22 11:57:30 -06:00
.gitignore [QT-705] Release enos 0.0.28 (#47) 2024-04-19 15:48:01 -06:00
.prettierignore copywrite: add copywrite headers support (#51) 2024-04-22 11:57:30 -06:00
action.yml release: enos 0.0.34 (#64) 2025-11-04 11:52:29 -07:00
eslint.config.js release: enos 0.0.34 (#64) 2025-11-04 11:52:29 -07:00
LICENSE release: enos 0.0.34 (#64) 2025-11-04 11:52:29 -07:00
package-lock.json security: override undici to 6.24.0 to resolve GHSA-v9p9-hfj2-hcw8 (#69) 2026-03-16 10:48:17 -06:00
package.json security: override undici to 6.24.0 to resolve GHSA-v9p9-hfj2-hcw8 (#69) 2026-03-16 10:48:17 -06:00
README.md release: enos 0.0.36 (#67) 2026-03-05 15:37:13 -07:00
vitest.config.mjs release: enos 0.0.34 (#64) 2025-11-04 11:52:29 -07:00

action-setup-enos

action-setup-enos downloads and installs the enos CLI into the runner environment.

Many enos CLI sub-commands require the terraform binary to be in the default PATH. You can install Terraform on the runner using the setup-terraform.

Important

Use setup-terraform@v3 or later, otherwise you'll need to set terraform-wrapper: false as the wrapper in prior versions will break the enos CLI's ability to execute terraform correctly.

Usage

steps:
  - name: Set up Terraform
    uses: hashicorp/setup-terraform@v3
  - name: Set up Enos
    uses: hashicorp/action-setup-enos@v1
    with:
      version: 0.0.36 # You only need to specify a version if you wish to override the default version

Inputs

The actions supports the following inputs:

  • version: The version of enos to install, defaulting to 0.0.36

Release a new version of Enos

  • Ensure that you have the latest version of Node 24 (krypton) installed
  • Ensure that you have installed the copywrite utility for writing copywrite headers.
  • Bump the version in package.json. This is the action version, not the enos cli version, it wont likely match the enos version
  • If we're releasing a new version of enos:
    • Change the latestVersion in src/enos.js to reflect the new version.
    • Update references to specific version in the README.md to the new version.
  • Run npm i && npm run all to compile, format, add license headers, lint, and test the action.
  • If all of the npm scripts pass then create a PR with the modified files.
  • Get review and the PR merged

After the pull request is merged it will automatically be released with the tagrelease Github Actions workflow.

Note

If for some reason you need to manually update the v1 tag you can do so with:

TAG="v$(cat package.json| jq -r '.version')"
git tag -a -m "$TAG" $TAG
git tag -a -m "$TAG" v1 -f
git push --tags -f