towncrier

Manage the release notes for your project.

Runssource: GitHubhomepagePythonMITcommit b8d90be2b1dc

Python, MIT licensed. The project labels itself: newsfile, project management, python, release automation and release notes.

towncrier runs. An Argusic agent installed it in 1 minute and hit no errors on a clean machine with no GPU, and the whole session was recorded.

towncrier 26.9.0.dev0 is installed in editable mode, all 168 tests pass, and the CLI correctly builds draft changelogs from news fragments without any real third-party credentials being required.

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 100 of 100 (the mean of this project's run scores).

At a glance

verdict
Runs
Argusic Score
100 / 100
cost of the verifying run
$0.01 (measured)
recorded runs
2
last tested
stars
932
forks
137
open issues
70
watchers
15
size
1 MB
created
last push

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.

Install time
1 minutes
Cold machine to finish
2 minutes
Errors hit and fixed
0 hit, 0 fixed with no human help
How the result was proved
python -m twisted.trial towncrier exited 0, 168 tests ran (164 passed, 4 skipped for missing mercurial). python -m towncrier build --draft --version 1.0.0 produced correct changelog output with the news fragment rendered.
Model tokens used
32,729
Exact commit tested
b8d90be2b1dc
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

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 verdict above comes from a different attempt, so read this as one session and not as the current result. 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.

- **test_depth**: tier1_real — no mocks or fake credentials needed; everything works with real code…
- **errors**: none.
- **notes**: 4 Mercurial tests are skipped because `hg` is not installed in the container — expecte…
tokens used
32,729
## Summary
- **install_succeeded**: true — `pip install -e ".[dev]"` completed without errors in a fresh venv.
- **launch_succeeded**: true — `python -m twisted.trial towncrier` ran 168 tests, all passed (164 s…
- **verified_how**: `python -m twisted.trial towncrier` exited 0 with 168 tests (164 passed, 4 skip…
- **test_depth**: tier1_real — no mocks or fake credentials needed; everything works with real code…
- **errors**: none.
- **notes**: 4 Mercurial tests are skipped because `hg` is not installed in the container — expecte…

Replay 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

  • Reached a running state on a clean machine, with the session recorded.
  • Installed in 1 minute.
  • Nothing broke on the way: zero errors between clone and running.
  • Ran without a GPU, so it does not need one to start.
  • Licensed MIT, as reported by its host.
  • Measured 2 times, so the result is not a one-off.

What it is a reasonable choice for

  • Trying it on a laptop or a small server: it reached a running state without a GPU.
  • A quick evaluation: it was running 1 minutes after the clone.
  • Following its own README: the documented path worked with nothing to fix.

Run history

tested byattemptoutcomescorecost USDwhen
Argusic Runner2/3Runs100.000.01
Argusic Runner1/3Runs100.000.01

Topics (from GitHub)

newsfileproject-managementpythonrelease-automationrelease-notes

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/towncrier.svg)](https://argusic.com/subject/towncrier)

Questions

Does towncrier run?
Yes. towncrier runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 0 errors on the way, and recorded the session.
How did Argusic test towncrier?
On a fresh, disposable machine, with every command recorded and the repository pinned at commit b8d90be2b1dc. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test towncrier?
The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does towncrier take to install?
1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does towncrier need a GPU?
Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing towncrier?
Nothing did, in the recorded run: zero errors between clone and running.
Where is the evidence for towncrier?
All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

Discussion