changesets/changesets

The inspected startup, add, version, and publish paths connect concrete command dispatch to their terminal effects. Additional traces cover status, prerelease persistence, and packing. These are source-derived execution sequences, not observed runtime results. Branches around skipped packages, prerelease state, authentication, and partial publication materially change the sequence.

• Startup: bin.js imports the CLI → index.ts calls cli.parse(run:false) → enables interactive guidance for TTY add/publish → displays the version intro → awaits runMatchedCommand; command actions import handlers lazily.
  packages/cli/bin.js#L3-9packages/cli/src/index.ts#L11-28packages/cli/src/cli.ts#L97-100
• Add: getPackages → ensureChangesetFolder → readConfig → filter versionable packages → best-effort getVersionableChangedPackages → createChangeset or empty intent → writeChangeset → optional getAddMessage/Git commit → optional launchEditor.
  packages/cli/src/commands/add/index.ts#L30-49packages/cli/src/commands/add/index.ts#L65-125packages/cli/src/commands/add/index.ts#L168-170
• Version: discover packages/read config → validate ignore names and skipped dependents → readChangesets/readPreState → reject snapshot/pre conflicts or absent intent → assembleReleasePlan → applyReleasePlan → optionally stage touched paths sequentially and commit.
  packages/cli/src/commands/version/index.ts#L27-70packages/cli/src/commands/version/index.ts#L72-125packages/cli/src/commands/version/index.ts#L127-143
• Planner: getRelevantChangesets rejects unknown packages and mixed skipped/non-skipped intent → getPreInfo → flattenReleases → build dependents graph → repeat determineDependents/matchFixedConstraint/applyLinks until stable → calculate output versions.
  packages/assemble-release-plan/src/index.ts#L138-183packages/assemble-release-plan/src/index.ts#L219-235packages/assemble-release-plan/src/index.ts#L249-280
• Status: getPackages/readConfig → readPreState/readChangesets → assembleReleasePlan → detect changed packages → enforce presence of changesets → either serialize the release plan or print sorted bump groups and optional IDs/new versions.
  packages/cli/src/commands/status/index.ts#L22-66packages/cli/src/commands/status/index.ts#L84-109
• Prerelease persistence: enterPre writes mode/tag → version application moves consumed files into .changeset/pre → active-pre assembly excludes archived IDs → exitPre writes mode:exit → the next application removes pre.json and consumes releasable archived intent.
  packages/pre/src/index.ts#L43-70packages/apply-release-plan/src/index.ts#L114-119packages/apply-release-plan/src/index.ts#L216-227packages/assemble-release-plan/src/index.ts#L279-283
• Pack: discover/read config → read supplied plan or compute getPublishPlan → create output/packages → queue publishTool.pack calls → hash each returned tarball → attach metadata to original chunks → write publish-plan.json; Yarn rejects publishConfig.directory.
  packages/cli/src/commands/pack/index.ts#L45-98packages/cli/src/commands/pack/index.ts#L110-158
• Publish: create reporter/discover adapter → load or compute plan → process dependency chunks → use TTY sequential probing or bulk publishing → recover eligible 2FA failures interactively → tag successes/tag-only entries → exit 1 for recorded failures.
  packages/cli/src/commands/publish/index.ts#L110-176packages/cli/src/commands/publish/index.ts#L191-265packages/cli/src/commands/publish/index.ts#L324-362packages/cli/src/commands/publish/index.ts#L376-419