Distillation

Date: July 21, 2026

• 🟡 (21:25) Read src/index.ts lines 75-116: main() function — strips dynamic-linker env vars via sanitizeDynamicLinkerEnv(), calls printVersion(), warnIfCraftEnvFileExists(), builds argv via fixGlobalBooleanFlags(process.argv.slice(2)), configures yargs with .env('CRAFT'), commands (prepare, publish, targets, config, artifacts, changelog), .option('log-level', ...), .middleware(setGlobals), then withTracing(main, { name: 'craft.cli', op: 'cli' })() at end of file.
• 🟡 (21:25) Read src/index.ts lines 1-74: imports include sanitizeDynamicLinkerEnv/warnIfCraftEnvFileExists from ./utils/env, envToBool/setGlobals from ./utils/helpers, getPackageVersion from ./utils/version, withTracing from ./utils/tracing, and command modules prepare/publish/targets/config/artifacts/changelog. GLOBAL_BOOLEAN_FLAGS defines 'no-input' (default isCI) and 'dry-run' (default process.env.DRY_RUN, TODO note to deprecate in favor of CRAFT_DRY_RUN). fixGlobalBooleanFlags() injects '1' after standalone boolean flags to work around yargs env-var/flag parsing shortcomings.
• 🟡 (21:26) Located setGlobals function definition at src/utils/helpers.ts:43.
• 🟡 (21:27) Read src/utils/helpers.ts lines 20-59: GlobalFlags interface ('dry-run'?, 'no-input'?, 'log-level'?), InternalGlobalFlags (required versions), GLOBAL_FLAGS defaults ('dry-run': false, 'no-input': false, 'log-level': 'Info'), setGlobals(argv) updates GLOBAL_FLAGS from argv and calls setLevel(LogLevel[...]), isDryRun() returns GLOBAL_FLAGS['dry-run'].
• 🟡 (21:27) [rejected-approach] Assistant decided against wiring setActiveWorkspace() call inside src/utils/helpers.ts setGlobals — would create circular import (helpers → config). Chose instead to add --workspace as a global yargs option in src/index.ts and call setActiveWorkspace via a middleware defined directly in index.ts.
• 🟡 (21:29) Edits applied to src/index.ts: added global --workspace CLI option and middleware wiring to call setActiveWorkspace (2 edits applied).
• 🟡 (21:31) Read src/config.ts lines 473-502: getGitTagPrefix() implementation — filters targets for name === 'github', takes first target's tagPrefix, warns via logger.warn if any github target's tagPrefix differs from the first (message: 'Multiple "github" targets with different "tagPrefix" values found...'), returns firstPrefix (empty string if none set).
• 🟡 (21:31) Edit applied to src/config.ts getGitTagPrefix() — added note that under workspaces the target list is already narrowed by the resolved config, so existing "first github target + warn" logic remains correct unchanged.
• 🟡 (21:31-21:32) tsc exit: 0 (clean). Existing config.test.ts suite: 1 test file passed, 20 tests passed (Duration 1.55s) — confirms backward compatibility of workspace resolver changes.
• 🟡 (21:33) Full test suite run: 58 test files passed, 1067 tests passed, 1 skipped (1068 total), Duration 30.27s — confirmed change is fully backward-compatible before adding new workspace tests.
• 🟡 (21:33) [requested-tests] Assistant proceeded to write tests for the new workspace resolver functionality, examining existing src/tests/config.test.ts structure to match patterns.
• 🟡 (21:34) Read src/tests/config.test.ts lines 1-60: imports getGitTagPrefix, loadConfigurationFromString, validateConfiguration from ../config, CraftProjectConfigSchema from ../schemas/project_config, logger from ../logger. describe('validateConfiguration') tests: parses minimal configuration, parses configuration with targets, parses configuration with changelog object, parses configuration with changelog string, parses configuration with versioning (calver policy, offset 14, format '%y.%-m').
• 🟡 (21:34) Read src/tests/config.test.ts lines 118-192: noMerge type validation tests; describe('getGitTagPrefix') block with helper loadWithTargets(targets) using loadConfigurationFromString with a YAML github/targets block; 6 tests covering empty prefix, single prefix, no-warn single target, no-warn matching prefixes, warn+first-prefix on differing prefixes, warn on mixed defined/undefined prefix.
• 🟡 (21:34) Assistant noted existing config.test.ts tests don't reset _activeWorkspaceName between runs (defaults to undefined, harmless for configs without workspaces) but new workspace tests must explicitly call setActiveWorkspace and reset state in afterEach to avoid cross-test leakage.
• 🟡 (21:35) Two edits applied to src/tests/config.test.ts adding a comprehensive workspaces test block (content not yet detailed in log).
• 🟡 (21:35-21:36) Bug identified: WORKSPACES_MIN_VERSION gate was set to '2.28.0', but checkMinimalConfigVersion() requires the running craft package version to be >= a config's declared minVersion — so any config declaring minVersion: 2.28.0 would fail checkMinimalConfigVersion under the current dev package version, before ever reaching the workspaces-specific gate. Root cause: gate value chosen without checking it against the actual current package version.
• 🟡 (21:36) Checked package.json: current version is "2.27.0-dev.0".
• 🟡 (21:36) Assistant framed two unresolved issues to fix: (1) test feasibility — tests can't exercise a real config through checkMinimalConfigVersion using minVersion 2.28.0 while running on 2.27.0-dev.0; (2) correct value for WORKSPACES_MIN_VERSION gate constant. Was reasoning toward setting WORKSPACES_MIN_VERSION to '2.27.0' (matching the imminent release) instead of '2.28.0', pending confirmation of how dev pre-release version strings compare — left unresolved at end of log.