Close Hermes v1.0.0 release checkpoint#89
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ebde3d6384
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
|
||
| Verification: the full Core suite passed with 419 tests, 16 existing warnings, and 4 subtests; focused Hermes tests passed; the wheel contains the Core runtime and plugin package data; docs command verification and strict MkDocs build passed; shell syntax, website parity, and repository diff checks passed. Live Hermes 0.18.2 validation normalized 16,296 local records without reading credential paths, installed and enabled the plugin, completed a background refresh, and reported a healthy launchd monitor. Desktop and mobile browser review confirmed the public command, copy action, responsive wrapping, and Hermes panel content. | ||
|
|
||
| Release acceptance: PRs #84 and #85 were merged after Python 3.10/3.11, MCP, SAST, secret, dependency, container, and Cloudflare checks passed. The immutable `v1.0.0` tag targets the verified release commit, the GitHub release and versioned container are published, and the public site and docs are live. `https://secopsai.dev/install.sh` returns the pinned standard installer and `https://secopsai.dev/install-hermes.sh` returns the Hermes 0.18.2+ installer. Cloudflare Pages now deploys the reviewed `website/` directory explicitly and rejects production deployments when either installer returns HTML or lacks its release marker. |
There was a problem hiding this comment.
Describe the installer check as post-deploy verification
When either public endpoint returns HTML or lacks its marker, .github/workflows/deploy-public-site.yml:31-40 has already completed wrangler pages deploy website; the checks do not run until lines 42-59. Their failure marks the GitHub job unsuccessful but does not reject or roll back the production Pages deployment, so this release checkpoint overstates the protection in place. Either perform validation before production promotion or describe this as post-deployment verification.
Useful? React with 👍 / 👎.
Summary
Record the completed production release acceptance for the Hermes Agent v1.0.0 integration, including the merged PRs, immutable release, public installer verification, Pages deployment gate, and final GitHub-plugin smoke test.
Verification