Skip to content

[persona-kit 8/8] Publish @agentworkforce/persona-kit@1.0.0 + workload-router major bump #71

@willwashburn

Description

@willwashburn

Part of the persona-kit consolidation. Depends on #69 and #70. This is issue 8 of 8 — the publish step.

Goal

Publish the new packages so the relay-side issue can pin against real npm versions instead of workspace:* linking.

Tasks

Pre-publish checks

Publish persona-kit

  • Confirm packages/persona-kit/package.json has:
    • "name": "@agentworkforce/persona-kit"
    • "version": "1.0.0"
    • "publishConfig": { "access": "public" }
    • "files" array including dist, README.md, package.json (no source files unless that's the local convention).
  • npm pack --dry-run from packages/persona-kit/ — verify the tarball contents look right (no source files leaked, no dist artifacts missing).
  • pnpm --filter @agentworkforce/persona-kit publish --tag latest (or the local equivalent — match how other packages publish from this monorepo).
  • Verify npm view @agentworkforce/persona-kit shows version 1.0.0 and the README renders correctly on npmjs.com.

Publish workload-router (major bump)

Deprecate harness-kit

Tag the release

Post-publish

  • Update the tracking issue ([persona-kit 1/8] Scaffold @agentworkforce/persona-kit package #64) with publish confirmation.
  • Notify the relay team (or unblock the relay-side issue) — relay can now pin @agentworkforce/persona-kit@^1.0.0.
  • If any external repos in the AgentWorkforce org still consume harness-kit (other than relay), open a follow-up tracking issue listing them — those need migration too.

Constraints

  • Don't npm unpublish @agentworkforce/harness-kit. Deprecate only. Unpublishing breaks lockfiles for any pinned consumer outside this repo.
  • Don't publish from a dirty working tree. CI-driven publish via the monorepo's normal release workflow is preferred over a manual npm publish from a developer laptop.
  • Match existing publish conventions in this monorepo (e.g., does it use changesets, lerna publish, manual scripts?). Don't introduce a new release tooling story in the same PR as the migration publish.

Verification

  • npm view @agentworkforce/persona-kit version returns 1.0.0.
  • npm view @agentworkforce/workload-router version returns the bumped major.
  • npm view @agentworkforce/harness-kit deprecated returns the deprecation message.
  • In a brand-new directory: npm install @agentworkforce/persona-kit resolves cleanly and exposes the documented top-level API.
  • import { buildPersonaSpawnPlan } from '@agentworkforce/persona-kit' from a fresh project compiles under TypeScript with the types declared.

Reference

Plan section 1.9.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions