v0.2.0-rc.2 — scope core under @mandarnilange + npm audit fix#5
Merged
Conversation
The framework package is renamed from `agentforge-core` to
`@mandarnilange/agentforge-core` so both published packages live
under one consistent npm scope. CLI binaries (`agentforge`,
`agentforge-core`) are unchanged — only install paths carry the
scope.
This drops the unscoped name's similarity-policy risk and makes
docs/install commands uniform across the stack. The unscoped
versions of `agentforge-core` (rc.0, rc.1) will be deprecated on
npm post-publish; they remain installable but redirect users to
the new path.
Also bumps `fast-xml-parser` via `npm audit fix` (XML-injection
advisory, transitive via OTel exporter → AWS SDK). Two `uuid <14`
audit warnings remain via dockerode 4.x — the advisory only
affects v3/v5/v6 with a caller-supplied buffer, which dockerode
never does (it uses v4). Documented in CHANGELOG and SECURITY;
fix lands in 0.3 once @types/dockerode@5 ships.
Touches:
- package.json + lockfile (root + per-package): rename + version bumps
- packages/platform/{package.json,src,tests}: import paths +
vitest alias + smoke-test assertions
- README, getting-started, CHANGELOG, ROADMAP, SECURITY,
CONTRIBUTING, packages/*/README, docs/*.md, issue templates,
release workflow header
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
1 participant
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.
Summary
agentforge-core→@mandarnilange/agentforge-core. Both published packages now live under one scope; install paths are uniform across the stack.agentforge,agentforge-core) unchanged — only npm install paths carry the scope.fast-xml-parservianpm audit fix(XML-injection advisory, transitive via AWS SDK). 2 of 4 audit warnings cleared.uuid <14advisory: only affectsv3/v5/v6with caller-supplied buffer; dockerode usesv4, so AgentForge is not exposed. Fix lands in 0.3 withdockerode@5once@types/dockerode@5ships.What changed
packages/core/package.json: name + versionpackages/platform/package.json: dep + peerDep keys + versionfrom "agentforge-core/..."→from "@mandarnilange/agentforge-core/..."Test plan
npm run typecheck— cleannpx vitest run— 1580 pass, 1 todonpx biome check .— cleanv0.2.0-rc.2: CI publishes both scoped packages + Docker images + GitHub Releasenpm deprecate agentforge-core@0.2.0-rc.0and0.2.0-rc.1pointing to@mandarnilange/agentforge-core