[ThomasK33]

Why

Ship the fixes merged since v0.1.0-beta.3 to npm, so downstream projects such as agent-tty can update. The consumer-visible change is #53: getNativeInfo() now reports the Ghostty commit the addon was built from (ghosttyCommit), and ghosttyVersion reads 0.1.0-dev+<commit>.

What changed

• package.json and package-lock.json go from 0.1.0-beta.3 to 0.1.0-beta.4. The branch name matches the version, so publish.yml creates v0.1.0-beta.4 after merge.
• The release-changelog workflow adds the CHANGELOG entry to this branch.

Scope

• Included since beta.3: fix(scripts): report the Ghostty commit in getNativeInfo #53 (Ghostty commit in getNativeInfo()), chore(deps): add a 7-day npm min-release-age #51 (7-day min-release-age for this repo's own npm installs, devEngines npm >= 11.10), fix(verify-libghostty-vt-node): refuse supplied libghostty-vt, check the addon hash, stop on failed writes #52 (verify skill scripts, not in the npm tarball), chore: sync verify-native-lifecycle to c54051e #50 (skill sync, not in the tarball).

Blast Radius

The merge publishes 0.1.0-beta.4 to npm under the beta dist-tag. latest stays on 0.1.0-beta.0. The tarball's package.json now carries devEngines. npm checks it only for the project it runs in, and the #51 verifier installed a packed tarball with npm 9.9.4, 10.8.2, 10.9.8 and 11.20.0 (all exit 0). .npmrc is not in the tarball.

Verification

• prepare-release-changelog.mjs prints should_generate=true and version-changed. resolve-npm-publish-tag.mjs prints beta.
• Local gate on this branch with Node 26.12.1: results posted as a PR comment.

---

Generated with xum • Model: anthropic:claude-opus-5-5 • Thinking: high