Issue Station
Sign In
Tools hereToolbox

hermes - ✅(Solved) Fix packaging/homebrew formula still points to 0.6.0 and contains placeholder sha256 [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
NousResearch/hermes-agent#19690•Fetched 2026-05-05 06:05:31
View on GitHub
Comments
0
Participants
1
Timeline
3
Reactions
0
Author
WadydXWadydX
Participants
WadydXWadydX
Timeline (top)
labeled ×2cross-referenced ×1

Root Cause

The Homebrew formula was likely added as release packaging scaffolding and then not updated with the current release asset/version and computed SHA256.

Fix Action

Fixed

PR fix notes

PR #19853: fix(homebrew): replace stale formula source and checksum for Hermes

Description (problem / solution / changelog)

Summary

  • Update packaging/homebrew/hermes-agent.rb from the broken 0.6.0 release asset URL to a valid source URL.
  • Replace placeholder sha256 with actual checksum for v2026.4.30 archive.
  • Add comment clarifying why the tagged archive is used until release asset attachment is restored.

Closes #19690

Changed files

  • packaging/homebrew/hermes-agent.rb (modified, +4/-4)
RAW_BUFFERClick to expand / collapse

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:

  1. Open packaging/homebrew/hermes-agent.rb from current main.
  2. Compare the formula source URL and SHA against the current package version.
  3. 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:

  1. update packaging/homebrew/hermes-agent.rb to the current release artifact and SHA256 during release, or
  2. 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.

extent analysis

TL;DR

Update the Homebrew formula to point to the current release asset and include the correct SHA256 value.

Guidance

  • Verify the current release asset URL and SHA256 value for version 0.12.0 to ensure accuracy.
  • Update packaging/homebrew/hermes-agent.rb to reference the current release asset and computed SHA256.
  • Consider adding documentation to clarify the release-time substitution step for the Homebrew formula.
  • Review prior packaging PRs and issues for potential guidance on updating the formula.

Example

# packaging/homebrew/hermes-agent.rb
url "https://github.com/NousResearch/hermes-agent/releases/download/v0.12.0/hermes_agent-0.12.0.tar.gz"
sha256 "computed_sha256_value"

Replace computed_sha256_value with the actual SHA256 value for the 0.12.0 release asset.

Notes

The provided information suggests that the Homebrew formula was not updated during the release process, leading to the stale formula. Ensuring the formula is updated with each release will prevent similar issues in the future.

Recommendation

Apply workaround: Update the Homebrew formula to point to the current release asset and include the correct SHA256 value, as this will allow for a functional installation process.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#installation#device allocation#model download#tokenizer error#prompt formatting

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

hermes - ✅(Solved) Fix packaging/homebrew formula still points to 0.6.0 and contains placeholder sha256 [1 pull requests, 1 participants]