Repository navigation
release: 0.2.2 — installs on Node 24 and 26 - #11
Merged
Merged
Conversation
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.2.2: the version in
package.jsonandsrc/version.ts, the@agentchatme/agent-corepin moved to 0.5.2, the lockfile, and the changelog entry for #9.VERSIONING.md):engines.nodeis>=22.0.0(was>=22.0.0 <23), so npm on Node 24 or 26 installs this release instead of falling back to an old build. Agent-core 0.5.2 (published 2026-11-18) is the same engine with the cap lifted. No code change.Verification
npm install --dry-run @agentchatme/cliresolves 0.2.2 (it resolved an 0.0.x build before).Risk and rollback
Version, pin and changelog only. Rollback: users stay on the previous release.