chart-releaser-action
A GitHub Action to turn a GitHub project into a self-hosted Helm chart repo, using helm/chart-releaser CLI tool
Runs with mockssource: GitHubhomepageShellApache-2.0commit 3e001cb8c689
Shell, Apache-2.0 licensed. The project labels itself: actions, charts, ci cd, github pages, helm, helm repositories and kubernetes.
chart-releaser-action runs, with stand-ins for the services it depends on. An Argusic agent installed it in 13 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The chart-releaser action installs cr v1.7.0 successfully, packages Helm charts, creates GitHub releases, and generates Helm repository index files; the upstream cr binary has a panic in GetPushURL for non-HTTPS git remotes that does not affect real GitHub usage
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.
- chart-releaser v1.7.0 GetPushURL panics on non-HTTPS git remote URLs
- RUNNER_TOOL_CACHE env var not set when running cr.sh outside GitHub Actions
- Install time
- 13 minutes
- Cold machine to finish
- 17 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- cr version returned v1.7.0; cr.sh install-only exited 0; cr.sh normal flow packaged chart, uploaded release to mock API (1 release, 1 asset verified via curl), and generated valid index.yaml with correct Helm chart metadata, digest, and URLs; upstream cr binary panics only on local git paths (non-HTTPS remote) in GetPushURL, this does not affect GitHub Actions
- Model tokens used
- 754,286
- Exact commit tested
- 3e001cb8c689
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
tokens used 754,286 Here's my final assessment and the structured report: ## Findings **What works:** - **Install**: `bash cr.sh --install-only` downloads `cr` v1.7.0 from GitHub releases, extracts it,… - **Package**: `cr package charts/mychart --package-path .cr-release-packages` produces a valid `my… - **Upload**: `cr upload` creates a GitHub release with chart asset — verified against a mock GitHu… - **Index**: `cr index` generates a valid Helm repository `index.yaml` with chart metadata, digest,… - **No-changes flow**: Running `cr.sh` on a repo without chart changes prints "Nothing to do" and e… - **Full `cr.sh` flow** (normal usage): packages the chart, creates the GitHub release (1 tag `mych… **The only runtime issue** is a panic in the upstream `chart-releaser` v1.7.0 `GetPushURL` function…
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
- Recovered from all 2 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, 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 13 minutes to install, slower than the median of the 10 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 11 actions projects Argusic has installed and timed, chart-releaser-action was the 10th fastest to reach a running state, and 6 of 11 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.03 |
Topics (from GitHub)
actionschartsci-cdgithub-pageshelmhelm-repositorieskubernetes
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/chart-releaser-action)Questions
- Does chart-releaser-action run?
- chart-releaser-action runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 13 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test chart-releaser-action?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 3e001cb8c689. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test chart-releaser-action?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does chart-releaser-action take to install?
- 13 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 chart-releaser-action need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing chart-releaser-action?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does chart-releaser-action compare with the alternatives?
- Of the 11 actions projects Argusic has installed and timed, chart-releaser-action was the 10th fastest to reach a running state, and 6 of 11 reached one at all.
- Where is the evidence for chart-releaser-action?
- 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.