Skip to content

Workspace Member v1 Migration

This is a breaking v1 migration from package-specific workspace additions to a workspace-member command.

Compatibility

  • repo-scaffold add-member is the v1 command.
  • repo-scaffold add-package NAME -p PATH remains as a deprecated alias with its existing flags and defaults.
  • New flags belong to add-member; the legacy command must not silently accept or reinterpret them.

Release

The migration is released as 1.0.0. The release commit must use a breaking Conventional Commit marker (feat!:) so Cocogitto computes the major release.

First delivery

  • pnpm members ts-lib, ts-cli, react-app, vue-app, react-lib, node-service, and electron-app are delivered by v1.
  • The initial member generated by template-pnpm-workspace is rendered through the same workspace_members/pnpm templates as later add-member calls.
  • Existing uv and Cargo library behavior remains available behind the same add-member domain model.
  • uv python-lib and Cargo rust-lib members are rendered from canonical templates under workspace_members, just like pnpm members.
  • Storybook remains a separate monorepo template and is intentionally deferred until the member templates stabilize.

Generated workspace workflow

New pnpm and Electron workspace templates contain .repo-scaffold.toml as workspace metadata and pin their task-runner integration to repo-scaffold==1.0.0:

just add-member agent-core ts-lib
just add-lib agent-core
just add-member release-tool ts-cli
just plan-member agent-core ts-lib

The CLI remains usable directly for automation or non-generated workspaces: