Skip to content

chore(codex): publish the Codex plugin 0.7.11 - #31

Merged
alwaysday1 merged 1 commit into
mainfrom
chore/codex_plugin_0_7_11
Nov 19, 2026
Merged

alwaysday1 merged 1 commit into
mainfrom
chore/codex_plugin_0_7_11

Conversation

@alwaysday1

Copy link
Copy Markdown
Collaborator

Summary

Syncs plugins/everme/ with the 0.7.11 plugin release. The npm packages (0.7.11) and evercli 0.33.18 are already published. Codex installs this plugin from this repository, so Codex users get 0.7.11 only after this merges.

  • .codex-plugin/plugin.json: version 0.7.10 to 0.7.11, so codex plugin marketplace upgrade picks up the change.
  • bin/hook.mjs and bin/memory-mcp.mjs: the bundles of the 0.7.11 release, byte-identical to the internal release commit.

.agents/plugins/marketplace.json, .claude-plugin/marketplace.json and plugins/claude-directory/ are unchanged.

Checks

  • Plugin version equals the bundles' release version (0.7.11).
  • Both bundles are byte-identical to the internal release commit.
  • git diff --check is clean; no internal hostnames, tokens or keys in the added lines.

🤖 Generated with Claude Code

Syncs plugins/everme with the 0.7.11 release (npm and evercli 0.33.18 are
already published):

- The hooks read their own brand's env file, so an EverMe and an EverOS
  install on one machine keep their own credentials.
- Pending turns from a session that ended before its Stop was committed
  are uploaded on the next Stop.
- Tool calls of other memory servers are left out of the upload.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@alwaysday1
alwaysday1 merged commit b35f03e into main Nov 19, 2026
7 checks passed
@alwaysday1
alwaysday1 deleted the chore/codex_plugin_0_7_11 branch November 19, 2026 09:58

@gloryfromca gloryfromca left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No blockers; this can merge as far as I am concerned.

Reviewed the complete origin/main...HEAD diff and the surrounding bundle entrypoints/callers, prior Codex publication history, backward-compatible MCP/tool/resource names, repository AGENTS.md rules, and whether the tests could mask the shipped artifact. I also rebuilt the executable portions from the public npm 0.7.11 sources: the hook matched exactly, and the MCP bundle matched after normalizing esbuild-only source-path labels. The manifest and both bundles agree on 0.7.11; syntax and hook startup checks passed.

Local plugin workspace tests passed and npm audit --audit-level=moderate reported zero vulnerabilities. The local runner lacks Go, so local CLI checks could not run (go: command not found); GitHub's cli-test, coverage, fast-gate, package-smoke, plugin-test, security, and aggregate results checks all passed. No tests were weakened in this diff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants