Skip to content

release: 0.3.0 — reply runs act as the agent itself: the own profile is the default; agent-core 0.6.0, manual 2.3.7 - #15

Merged
sanctrl merged 1 commit into
mainfrom
release/0.3.0
Nov 19, 2026
Merged

sanctrl merged 1 commit into
mainfrom
release/0.3.0

Conversation

@sanctrl

@sanctrl sanctrl commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

What changes

Release 0.3.0. This PR sets the version (package.json, src/version.ts), pins @agentchatme/agent-core 0.6.0 exactly (lockfile refreshed from npm), and opens ## 0.3.0 — 2026-11-19 in the changelog. Because it adds behaviour, this is a minor +1 (VERSIONING.md).

  • What ships: feat(listen): presets default to own — runs act as the agent itself #13. Reply runs act as the agent itself: the default run profile is own, and answer stays as the explicit lock. It also ships fallback manual 2.3.7 from the engine.
  • Changelog repair: when feat(listen): presets default to own — runs act as the agent itself #13 merged, git put its entry inside the already-published 0.2.3 section. This PR moves it into 0.3.0, so the 0.2.3 section is byte-for-byte what 0.2.3 shipped. It also drops the line "Needs the agent-core release that adds own", which this pin makes true.
  • Upgrade: users switch when they run the upgrade (npx -y @agentchatme/<package> or doctor --fix), which re-copies the service bundle and restarts it.

Verification

  • Tests: local on Node 22 against agent-core 0.6.0 from npm: type-check, build, tests 100 passed, 1 skipped (101).
  • Review: not needed: a version bump, an exact pin and a changelog move for code reviewed in feat(listen): presets default to own — runs act as the agent itself #13.
  • Live check: after publish, npm view should show 0.3.0. Then an own run on the lab coding box.

…is the default; agent-core 0.6.0, manual 2.3.7
@sanctrl
sanctrl enabled auto-merge (squash) November 19, 2026 17:33
@sanctrl
sanctrl merged commit 528874d into main Nov 19, 2026
5 checks passed
@sanctrl
sanctrl deleted the release/0.3.0 branch November 19, 2026 17:46
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