Cairn

Unversioned config migration overwrites user values

NousResearch/hermes-agent · cluster 120813

Data as of

Nothing open on GitHub. Fix merged in #121251. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #121251. 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
Nothing open on GitHub.

These items address a bug where configs lacking a version stamp are incorrectly run through the full migration ladder, causing user-set values to be overwritten. The work involves fixes to migration logic, schema provenance ownership, and preservation of unstamped user settings.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

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

  • #121251 hermes update no longer rewrites user values in unversioned configs (#120813, salvage #120814)

    merged to main

    files: cli-config.yaml.example, hermes_cli/config.py, hermes_cli/config_migrations.py, scripts/docker_config_migrate.py, tests/hermes_cli/test_config.py, tests/hermes_cli/test_config_unversioned_migration.py, tests/tools/test_docker_config_migrate.py

3 PRs closed without merging

From the close comments: done elsewhere 2 · superseded by another PR 1

  • #120814 fix(config): stop the migration ladder rewriting unversioned configs · done elsewhere → 38bf40a, ab1fa99, 4b9bda7, f30b147, c58dad4, 03584e4, #121251
  • #120939 fix(config): preserve unstamped user settings during migration · superseded by another PR → #121026, #120814
  • #121026 fix(config): make the writer own schema provenance · done elsewhere → ab1fa99, 03584e4, #121251, #120814
Closed issues · 1
  • Closed#120813[Bug]: first update of a config.yaml without _config_version runs the whole migration ladder and rewrites user values
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.40: 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

Merged PRs
#121251
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
24 Sep 2026

For your agent

The same facts, typed.

cluster/120813.json
cluster/120813.md