release: integrate Zeus v0.6.0 and Hermes 0.21 workflows - #41
Merged
Merged
Conversation
….6-operator-workflows
This was referenced Sep 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Integrate Zeus 0.6.0 with Hermes Agent 0.21 compatibility, graceful owned-gateway shutdown, authenticated live diagnostics and durable operator messaging. The combined stack includes #42, #43 and #44; package metadata, schema-9 upgrade guidance and release checks are included.
Messaging remains opt-in, with bounded authenticated requests, durable idempotency receipts and explicit recovery when an acknowledged job's outcome is unavailable. Release publication requires successful CI from the exact tagged main commit, plus verified commit and tag signatures. Both release verifiers close HTTP error responses without exposing sensitive response data.
Resolve the ancestry introduced by the #23 squash merge without changing the tested source: current main has the same tree as #23's original head, and the final combined branch has exactly the same file tree as validated candidate
2d70de386548a0bba9c3852b840423173a48d8c1.Validation:
make release-check; subsequent HTTP cleanup passed 28 focused tests on Python 3.13 and 3.14 with zero ResourceWarnings.git diff --checkpassed. Fresh CI on the combined branch is required before main promotion.Schema 9 is additive. Back up database and profile state before upgrading; rollback requires the pre-upgrade backup and old package. Provider-backed workloads and release-tag publication have not been performed by this validation.