harald/nixcfg
1
0
Fork 0
Code Issues Pull requests 5 Projects Releases Packages Wiki Activity Actions

feat(hermes): pin hermes-agent input to release v2026.9.24 #55

Open
hermes wants to merge 1 commit from hermes/hermes-agent-v2026.9.24 into main AGit
pull from: hermes/hermes-agent-v2026.9.24
merge into: harald:main
Conversation 1 Commits 1 Files changed 2 +9 -4
hermes commented 2026-10-08 09:26:02 +02:00
Contributor
Copy link

Update the hermes-agent flake source from the floating github url (was
locked at b5251aa, 2026-09-20 main) to the latest upstream release tag
v2026.9.24 (f97608f, package version 0.21.5). Pinning the tag in the url
makes bumps deliberate — 'nix flake update' alone can no longer silently
wander along the rolling main.

Verified: nix flake check --no-build green, hermes-agent 0.21.5 package
builds, nextcloud-talk-platform plugin builds with its 215 pytest checks
against the new rev.

Update the hermes-agent flake source from the floating github url (was locked at b5251aa, 2026-09-20 main) to the latest upstream release tag v2026.9.24 (f97608f, package version 0.21.5). Pinning the tag in the url makes bumps deliberate — 'nix flake update' alone can no longer silently wander along the rolling main. Verified: nix flake check --no-build green, hermes-agent 0.21.5 package builds, nextcloud-talk-platform plugin builds with its 215 pytest checks against the new rev.
feat(hermes): pin hermes-agent input to release v2026.9.24
All checks were successful
nix flake check / flake-check (pull_request) Successful in 4m28s
Details
2ff225633e 
Update the hermes-agent flake source from the floating github url (was
locked at b5251aa, 2026-09-20 main) to the latest upstream release tag
v2026.9.24 (f97608f, package version 0.21.5). Pinning the tag in the url
makes bumps deliberate — 'nix flake update' alone can no longer silently
wander along the rolling main.

Verified: nix flake check --no-build green, hermes-agent 0.21.5 package
builds, nextcloud-talk-platform plugin builds with its 215 pytest checks
against the new rev.
hermes commented 2026-10-08 09:29:20 +02:00
Author
Contributor
Copy link

Direction check (the compare API read the right way round):

  • The previously locked rev b5251aa (main, 2026-09-20) is a strict ANCESTOR of the tag: compare/v2026.9.24...b5251aa → status=behind, ahead_by=0. So this is a clean forward bump — the tag adds 2883 commits and drops none.
  • v2026.9.24 (f97608f) is the latest published release (v0.21.5). Upstream main is 9141 commits ahead of the tag with no newer release, so staying on the floating url meant tracking unreleased main. Pinning the tag in the url makes future bumps deliberate.

Side finding, deliberately NOT fixed here (flake-only, per the no-unrelated-changes criterion):

  • Upstream DEFAULT_CONFIG _config_version is 45 at the old lock and 46 at v2026.9.24, while services.hermes-agent.settings._config_version (systems/x86_64-linux/hermes/default.nix) stamps 33 — never bumped since the VM was added in db9a23c, and the running host (0.21.3, config.yaml _config_version: 33) already has that drift. A bump should be its own change with the migration-ladder semantics checked (LEGACY_KEY_STEPS applies only to unversioned configs; under HERMES_MANAGED migrations run in-memory and only the stamp persists).

Verification on this head: nix flake check --no-build green (all nixosConfigurations + darwin + package checks), .#nixosConfigurations.hermes.config.services.hermes-agent.package builds → hermes-agent-0.21.5, nextcloud-talk-platform builds with its full pytest suite (215 passed) against the new rev.

Direction check (the compare API read the right way round): - The previously locked rev b5251aa (main, 2026-09-20) is a strict ANCESTOR of the tag: `compare/v2026.9.24...b5251aa` → status=behind, ahead_by=0. So this is a clean forward bump — the tag adds 2883 commits and drops none. - v2026.9.24 (f97608f) is the latest published release (v0.21.5). Upstream main is 9141 commits ahead of the tag with no newer release, so staying on the floating url meant tracking unreleased main. Pinning the tag in the url makes future bumps deliberate. Side finding, deliberately NOT fixed here (flake-only, per the no-unrelated-changes criterion): - Upstream DEFAULT_CONFIG `_config_version` is 45 at the old lock and 46 at v2026.9.24, while `services.hermes-agent.settings._config_version` (systems/x86_64-linux/hermes/default.nix) stamps 33 — never bumped since the VM was added in db9a23c, and the running host (0.21.3, config.yaml `_config_version: 33`) already has that drift. A bump should be its own change with the migration-ladder semantics checked (LEGACY_KEY_STEPS applies only to unversioned configs; under HERMES_MANAGED migrations run in-memory and only the stamp persists). Verification on this head: `nix flake check --no-build` green (all nixosConfigurations + darwin + package checks), `.#nixosConfigurations.hermes.config.services.hermes-agent.package` builds → hermes-agent-0.21.5, `nextcloud-talk-platform` builds with its full pytest suite (215 passed) against the new rev.
All checks were successful
nix flake check / flake-check (pull_request) Successful in 4m28s
Details
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin +refs/pull/55/head:hermes/hermes-agent-v2026.9.24
git switch hermes/hermes-agent-v2026.9.24
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
harald/nixcfg!55
No description provided.