Skip to content

Version Packages#45

Merged
creatornader merged 2 commits into
mainfrom
changeset-release/main
May 22, 2026
Merged

Version Packages#45
creatornader merged 2 commits into
mainfrom
changeset-release/main

Conversation

@github-actions
Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@atrib/emit@0.12.0

Minor Changes

  • 197b52c: Add atrib-emit-cli binary (D082): a thin command-line wrapper around emitInProcess that reads a JSON envelope from stdin, signs the record in-process, and writes the EmitOutput JSON to stdout. Exit code is always 0 per the §5.8 degradation contract; failures surface as warnings inside the result or as a stderr diagnostic line.

    Per D082, this binary replaces the D081 "import @atrib/emit from the hook helper" integration shape. Operators install @atrib/emit globally (npm install -g @atrib/emit) and the hook helper spawns atrib-emit-cli instead of carrying a local node_modules/. Removing the npm workspace from the hook source directory eliminates a failure mode where Claude Code silently dropped hooks while the directory's package files were mutating.

    Records signed via the CLI are byte-identical to MCP-server-signed and middleware-signed records (same canonical form per §1.3, same handleEmit path, same resolveKey with the bounded ATRIB_KEYCHAIN_TIMEOUT_MS / ATRIB_OP_TIMEOUT_MS from D081). The existing atrib-emit MCP-server binary is unchanged.

@atrib/annotate@0.2.6

Patch Changes

  • Updated dependencies [197b52c]
    • @atrib/emit@0.12.0

@atrib/revise@0.2.6

Patch Changes

  • Updated dependencies [197b52c]
    • @atrib/emit@0.12.0

github-actions Bot and others added 2 commits May 22, 2026 15:19
The changesets bot uses GITHUB_TOKEN to open Version Packages PRs;
GITHUB_TOKEN cannot trigger workflows recursively, so 5 of 10 required
checks never fire on the auto-opened PR. An empty signed commit pushed
from a real user (or signed bot identity) re-triggers them.
@creatornader creatornader merged commit 62b06de into main May 22, 2026
12 checks passed
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.

1 participant