Distillation

Date: Aug 25, 2026

• 🟡 (14:52) Inspected /home/byk/Code/getsentry/craft/src/utils/publishState.ts (110 lines). Publish-resume state was moved from repository-local .craft-publish-<version>.json to $XDG_STATE_HOME/craft/, falling back to $HOME/.local/state/craft/, to prevent committed repository contents or prior CI steps from pre-populating completed targets and causing silent skips. getCraftStateDir() uses XDG_STATE_HOME when non-empty, otherwise homedir()/.local/state/craft.
• 🟡 (14:52) In /home/byk/Code/getsentry/craft/src/utils/publishState.ts, getPublishStateFilename(version, githubConfig, cwd = process.cwd()) sanitizes strings by lowercasing and replacing non-[a-z0-9._-] runs with _, trimming edge underscores. With GitHub config it returns publish-state-<owner>-<repo>-<sha1(cwd)[:12]>-<version>.json; without GitHub config it returns publish-state-<sha256(cwd)[:16]>-<version>.json. getPublishStatePath() joins this filename to getCraftStateDir().
• 🟡 (14:53) Tool listed 34 entries under /home/byk/Code/getsentry/: cli-api-1423/, cli-wt/, cli/, codecov-action/, craft-vercel-prebuilt-output/, craft-vercel-project-config/, craft-workspace-action-propagation/, craft-workspaces-schema/, craft/, devinfra-coder-infra/, devinfra-deployment-service/, getsentry/, ops/, package_grant_publish_repo/, publish-workspace-acceptance/, publish/, security-as-code/, self-hosted/, sentry-api-schema/, sentry-docs/, sentry-forge/, sentry-go/, sentry-javascript/, sentry-orbital/, sentry-python/, sentry-release-registry/, sentry-wizard/, sentry/, snuba/, spotlight/, sqlish/, static-sites/, stripe-app/, symbolic/.
• 🟡 (14:54) Search of /home/byk/Code/getsentry/craft-workspace-action-propagation/action.yml found 11 workspace-related matches: input workspace at lines 34–35 is described as “Named Craft release workspace to prepare and publish”; WORKSPACE is passed from ${{ inputs.workspace }} at lines 168, 202, and 231; Craft arguments append/use --workspace "$WORKSPACE" at lines 185 and 206; issue title handling JSON-encodes workspace with jq -Rn --arg workspace "$WORKSPACE" '$workspace' and adds [workspace: ${workspace_json}] at lines 258–265.
• 🔴 (14:55) User stated package management must always use pnpm; npm and yarn must never be used.
• 🔴 (14:55) User stated Craft uses Node.js managed by Volta, currently v22.12.0; dependencies are installed with pnpm install --frozen-lockfile.
• 🟡 (14:55) Coding guidance inspected for Craft: TypeScript is used throughout; Prettier 3.x uses single quotes and no arrow parentheses via .prettierrc.yml; ESLint 9.x uses flat config in eslint.config.mjs with typescript-eslint; unused variables prefixed _ are allowed. Mutating operations must use getGitClient()/createGitClient() for Git, getGitHubClient() for GitHub API, safeFs.writeFile()/safeFs.unlink() rather than raw fs, or safeExec(action, description) for custom operations.
• 🟡 (14:56) Inspected modified /home/byk/Code/getsentry/craft-workspace-action-propagation/src/utils/publishState.ts (121 lines). getPublishStateFilename() and getPublishStatePath() now accept optional workspace?: string; when present it adds workspace-${Buffer.from(workspace).toString('base64url')}- immediately before sanitized version in both GitHub-config and cwd-hash-only filenames. This losslessly encoded workspace prefix isolates completed-target resume state for independent same-repository, same-version release workspaces.
• 🔴 (14:56) User stated a subsequent option such as --workspace --dry-run must never be mistaken for a workspace name.
• 🟡 (14:56) Search found /home/byk/Code/getsentry/craft-workspace-action-propagation/src/utils/workspaces.ts supports workspace discovery from package.json npm/yarn workspaces and pnpm-workspace.yaml; it detects workspace packages/dependencies and topologically sorts them, reporting circular dependencies. Search also confirmed workspace-aware publish state in src/utils/publishState.ts and workspace selection parsing in src/utils/helpers.ts.
• 🟡 (14:58) Inspected /home/byk/Code/getsentry/craft-workspace-action-propagation/src/utils/helpers.ts lines 1–140. MAX_STEP_OUTPUT_BYTES = 64 * 1024; envToBool() treats '', 'undefined', 'null', '0', 'false', and 'no' as false. extractWorkspaceSelection(argv, env = process.env) reads CRAFT_WORKSPACE, parses raw argv using Node parseArgs() with { workspace: { type: 'string' } }, allowPositionals: true, strict: false, and tokens: true.
• 🟡 (14:58) extractWorkspaceSelection() in src/utils/helpers.ts supports --workspace foo and --workspace=foo; last --workspace occurrence wins, but a bare/empty final flag clears earlier CLI selection and falls back to CRAFT_WORKSPACE. It accepts a token value only if non-empty and either inline or not prefixed with -; therefore --workspace=-foo is valid while --workspace --foo is not.
• 🟡 (14:58) Search found resolveWorkspaceConfig at line 110 and its call at line 239 in /home/byk/Code/getsentry/craft-workspace-action-propagation/src/config.ts.
• 🟡 (15:00) Inspected /home/byk/Code/getsentry/craft-workspace-action-propagation/src/config.ts lines 80–269. setActiveWorkspace(name) sets _activeWorkspaceName and invalidates _configCache and _globalGitHubConfigCache; getActiveWorkspace() returns the active workspace.
• 🟡 (15:00) In resolveWorkspaceConfig(base, workspaceName), unknown workspaces throw ConfigurationError listing available workspaces or stating none are defined. Workspace release-relevant fields shallowly override base fields; workspaces and minVersion are omitted from the resolved config. github is shallow-merged so a workspace can override projectPath while inheriting owner/repo; if merged GitHub config lacks owner or repo, github is removed so getGlobalGitHubConfig() can fall back to Git remote detection.
• 🟡 (15:00) applyWorkspaceSelection(config) in src/config.ts returns config unchanged when no workspaces and no active selection; errors if --workspace/active selection is provided without defined workspaces; errors when workspaces exist but none is explicitly selected, instructing --workspace <name> or CRAFT_WORKSPACE; and requires config.minVersion >= WORKSPACES_MIN_VERSION before resolving the selected workspace. SemVer build metadata is stripped before compatibility comparisons because the comparison helper rejects versions containing build metadata.
• 🟡 (15:02) Inspected /home/byk/Code/getsentry/publish-workspace-acceptance/src/publish/inputs.js (13 lines): inputs() calls detailsFromContext({ context: github.context }) and writes the result with core.setOutput('result', result).
• 🟡 (15:02) Search found workspace-protocol coverage in /home/byk/Code/getsentry/craft-workspace-action-propagation/src/__tests__/versionBump.test.ts, including describe('workspace:* handling (issue #804)', ...), fixtures using @scope/core: 'workspace:*', simulated npm error code EUNSUPPORTEDPROTOCOL / Unsupported URL Type "workspace:", and assertions that nested dependency pins remain "workspace:*". Search also found selected-workspace config resolution coverage in src/__tests__/config.test.ts line 265.
• 🟡 (15:03) Tool search returned “No files found” for an unspecified query.
• 🟡 (15:04) Search found publish-workspace acceptance context logic in /home/byk/Code/getsentry/publish-workspace-acceptance/src/modules/details-from-context.js at line 19 and tests in src/modules/__tests__/details-from-context.js at lines 3, 38, 50, 93, 105, 127, 147, 164, 176, and 198.
• 🟡 (15:05) Inspected /home/byk/Code/getsentry/publish-workspace-acceptance/src/publish/update-issue.js (9 lines): it imports updateIssue, gets an Octokit client using github.getOctokit(getGitHubToken()), parses process.env.PUBLISH_ARGS as JSON, and calls updateIssue({ context: github.context, octokit, inputs }).
• 🟡 (15:07) Inspected /home/byk/Code/getsentry/publish-workspace-acceptance/src/modules/update-issue.js (78 lines). updateTargets() currently reads repository-local state from ${process.env.GITHUB_WORKSPACE}/__repo__/.craft-publish-${version}.json; if absent it returns. If present, it concurrently fetches the issue and parses state JSON, then updates the issue body using transformIssueBody().
• 🟡 (15:07) In update-issue.js, transformIssueBody(craftState, issueBody) updates target checkboxes in TARGETS_SECTION_PARSER_REGEX using TARGETS_PARSER_REGEX; declared target IDs become - [x] <target> when craftState.published[targetId] is truthy, otherwise - [ ] <target>. Published targets absent from the declared section are appended. updateIssue() derives version, context.repo, and context.payload.issue.number, then concurrently updates targets and removes the "accepted" issue label.