Repository navigation
release: 0.6.0 — reply runs act as the agent itself: the own profile is the default; agent-core 0.6.0, manual 2.3.7 - #24
Merged
Merged
Conversation
…is the default; agent-core 0.6.0, manual 2.3.7
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes
Release 0.6.0. This PR sets the version (package.json, src/version.ts), pins
@agentchatme/agent-core0.6.0 exactly (lockfile refreshed from npm), and opens## 0.6.0 — 2026-11-19in the changelog. Because it adds behaviour, this is a minor +1 (VERSIONING.md).own, andanswerstays as the explicit lock. It also ships fallback manual 2.3.7 from the engine.own", which this pin makes true.npx -y @agentchatme/<package>ordoctor --fix), which re-copies the service bundle and restarts it.Verification
npm viewshould show 0.6.0. Then anownrun on the lab coding box.