Bug Description
The checked-in Homebrew formula under packaging/homebrew/ appears stale and non-installable as-is.
It points to the old hermes_agent-0.6.0.tar.gz release asset and still contains the placeholder SHA256 value <replace-with-release-asset-sha256>, while the current package version in the repo is 0.12.0.
Inspected against main commit af6f9bc2a12682b06fb3632acf5a9cbf01e74a85.
Steps to Reproduce
Static packaging path:
- Open
packaging/homebrew/hermes-agent.rb from current main.
- Compare the formula source URL and SHA against the current package version.
- Try to use/audit the formula as checked in.
Expected Behavior
The repo-provided Homebrew formula should either:
- point at the current release asset with a real SHA256; or
- be clearly marked as a template/example that is not expected to install without release-time substitution.
Actual Behavior
The formula points at an old release asset and contains a placeholder SHA256 value.
Evidence
packaging/homebrew/hermes-agent.rb:8
url "https://github.com/NousResearch/hermes-agent/releases/download/v2026.3.30/hermes_agent-0.6.0.tar.gz"
packaging/homebrew/hermes-agent.rb:9
sha256 "<replace-with-release-asset-sha256>"
pyproject.toml:7
- current project version is
0.12.0.
hermes_cli/__init__.py:17-18
- current CLI version is
0.12.0, release date 2026.4.30.
Affected Component
Setup / Installation / Packaging
Environment
Static analysis of current main; no local environment-specific behavior required.
Prior Art Checked
I searched existing issues and PRs for:
replace-with-release-asset-sha256
hermes_agent-0.6.0.tar.gz
Homebrew 0.12.0 0.6.0
- broader Homebrew/brew packaging terms
I found older Homebrew packaging work, including the original Homebrew formula request and packaging PRs, but no exact current issue for the stale formula URL plus placeholder SHA.
Root Cause Analysis
The Homebrew formula was likely added as release packaging scaffolding and then not updated with the current release asset/version and computed SHA256.
Proposed Fix
Either:
- update
packaging/homebrew/hermes-agent.rb to the current release artifact and SHA256 during release, or
- rename/comment the file clearly as a template and document the release-time substitution step so users do not treat it as a working formula.
Bug Description
The checked-in Homebrew formula under
packaging/homebrew/appears stale and non-installable as-is.It points to the old
hermes_agent-0.6.0.tar.gzrelease asset and still contains the placeholder SHA256 value<replace-with-release-asset-sha256>, while the current package version in the repo is0.12.0.Inspected against
maincommitaf6f9bc2a12682b06fb3632acf5a9cbf01e74a85.Steps to Reproduce
Static packaging path:
packaging/homebrew/hermes-agent.rbfrom currentmain.Expected Behavior
The repo-provided Homebrew formula should either:
Actual Behavior
The formula points at an old release asset and contains a placeholder SHA256 value.
Evidence
packaging/homebrew/hermes-agent.rb:8url "https://github.com/NousResearch/hermes-agent/releases/download/v2026.3.30/hermes_agent-0.6.0.tar.gz"packaging/homebrew/hermes-agent.rb:9sha256 "<replace-with-release-asset-sha256>"pyproject.toml:70.12.0.hermes_cli/__init__.py:17-180.12.0, release date2026.4.30.Affected Component
Setup / Installation / Packaging
Environment
Static analysis of current
main; no local environment-specific behavior required.Prior Art Checked
I searched existing issues and PRs for:
replace-with-release-asset-sha256hermes_agent-0.6.0.tar.gzHomebrew 0.12.0 0.6.0I found older Homebrew packaging work, including the original Homebrew formula request and packaging PRs, but no exact current issue for the stale formula URL plus placeholder SHA.
Root Cause Analysis
The Homebrew formula was likely added as release packaging scaffolding and then not updated with the current release asset/version and computed SHA256.
Proposed Fix
Either:
packaging/homebrew/hermes-agent.rbto the current release artifact and SHA256 during release, or