terraform-module-releaser
GitHub Action to automate versioning, releases, and documentation for Terraform modules in monorepos.
Runs with mockssource: GitHubTypeScriptMITcommit 5260b01ca93b
TypeScript, MIT licensed. The project labels itself: continuous integration, devops tools, github action, release automation, terraform, terraform module and wiki.
terraform-module-releaser runs, with stand-ins for the services it depends on. An Argusic agent installed it in 3.5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
npm install succeeds, TypeScript compiles clean, and 814 of 821 tests pass on Node 24 with terraform-docs v0.21.0 installed to ~/.local/bin/. The 4 skipped/failed suites are GitHub API integration tests requiring a real GITHUB_TOKEN.
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 92 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Container has Node 18 but project requires Node >=24. Downloaded Node 24 binary and used it via PATH override.1.5 minutes
- installTerraformDocs() hardcodes sudo to install terraform-docs to /usr/local/bin, but sudo is not available in the container.1 minute
- terraform-docs binary not pre-installed. Tests that exercise terraform-docs generation fail without it.0.5 minutes
- Install time
- 4 minutes
- Cold machine to finish
- 4 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- npm test exited with code 1 (expected: 4 suites fail due to missing GITHUB_TOKEN for real GitHub API tests), 814 passed, 0 actual failures, 7 skipped, 0 type errors. TypeScript compilation (tsc --noEmit) exited 0 with no errors.
- Model tokens used
- 145,830
- Exact commit tested
- 5260b01ca93b
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
- Behaviour against real services
- this run was verified against stand-in services only
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 1, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
26| }
27| await context.useRealOctokit();
⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[4/4]⎯
Test Files 4 failed | 19 passed (23)
Tests 814 passed | 7 skipped (821)
Type Errors no errors
Start at 10:19:55
Duration 3.27s (tests 43%, setup 32%, transform 13%, import 7%, worker 4%)
Isolate 23 workers spawned · ~74ms startup each (spawn + environment, per file)
at least ~490ms faster with isolate: false — reuses workers across files instead of on…
tokens used
145,830Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Took 3.5 minutes to install, slower than the median of the 3 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 4 continuous-integration projects Argusic has installed and timed, terraform-module-releaser was the 3rd fastest to reach a running state, and 1 of 4 reached one at all.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 1/3 | Runs with mocks | 92.00 | 0.07 |
Topics (from GitHub)
continuous-integrationdevops-toolsgithub-actionrelease-automationterraformterraform-modulewiki
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/terraform-module-releaser)Questions
- Does terraform-module-releaser run?
- terraform-module-releaser runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 4 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test terraform-module-releaser?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 5260b01ca93b. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test terraform-module-releaser?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does terraform-module-releaser take to install?
- 3.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does terraform-module-releaser need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing terraform-module-releaser?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does terraform-module-releaser compare with the alternatives?
- Of the 4 continuous-integration projects Argusic has installed and timed, terraform-module-releaser was the 3rd fastest to reach a running state, and 1 of 4 reached one at all.
- Where is the evidence for terraform-module-releaser?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.