NousResearch/hermes-agent

ffmpeg pinned build expiry and re-pin handling

Cluster 122240 · hermes cli. Data as of 2026-10-27 11:58 UTC

1 open item. Fix merged in #125468 on 27 Sep 2026. Check it covers your case.

open issues

open PR

items grouped

Known?: Yes. 6 related items grouped here, 1 issue already closed.
Fix event: A fix was merged to main in PR #125468. Check it covers your case. No release data is tracked.
Tracker: The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open: 0 issues and 1 PR.

Next step: read #125468, then check it covers your case.

Read #125468 Pick up a Lab task

These issues and PRs address a recurring problem where pinned ffmpeg autobuild assets from BtbN expire or get deleted by the supplier, causing 404 errors. The work explores strategies for detecting and recovering from expired pins, including local re-pinning and selecting more stable build targets.

Open issues0

No open issues.

Open PRs1

PR#122262fix(pm): repin expired ffmpeg autobuild assets

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

#125468 ffmpeg installs stop expiring: pin BtbN's retained month-end build, and pm update only picks those (#125350)

merged to main

files: pm/lock.json, pm/packages.py, pm/update.py, tests/pm/test_ffmpeg_resolution.py, tests/pm/test_update_request_reuse.py

3 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1 · other 1

#122433 fix(pm): re-pin artifacts whose pinned archive the supplier retired (#122240) · merged via another change → #125510, #125468
#125510 Installs survive a supplier deleting the pinned build: machine-local re-pin, never lock.json (#122240, salvage #122433) · superseded by another PR → #125468
#125527 fix(pm): keep retired artifact repairs with verified realizations · other → #125510, #125468

Closed issues · 1

Closed#122240[Bug]: ffmpeg lock.json points to expired BtbN autobuild (404)

How this cluster was grouped

Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
Pairwise link density 0.33: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Subsystem: hermes cli
Merged PRs: #125468
Closed issues: 1
Attempts: 3 PRs closed without merging
Fix link checked: 27 Sep 2026

For your agent

The same facts, typed.

cluster/122240.json
cluster/122240.md