Distillation

Date: Sep 3, 2026

• 🟡 (15:54) Git branch/status in /home/byk/Code/getsentry/publish-workspace-acceptance: feat/workspace-acceptance...origin/feat/workspace-acceptance; modified files remain src/modules/post-workflow-details.js and src/publish/inputs.js.
• 🟡 (15:54) Recent commits listed: 52ef600 feat: resolve compact workspace publish requests; b658ffa fix: validate publish workspace JSON; 33de3f1 feat: accept workspace publish requests; 83d210b build(deps): bump js-yaml from 4.3.0 to 4.3.1 (#9174); 5268a23 feat: Add Vercel creds.
• 🔴 (15:57) User specified error-handling convention: always throw for unexpected values, including a default switch case such as throw new Error(\Unknown status: '${status}'`);`.
• 🟡 (15:57) AGENTS.md states this repository is the Sentry Publish Repository: a GitHub Actions-based approval system for publishing releases across multiple Sentry projects using Craft; it is pure JavaScript on Node.js 24.0.0 using CommonJS modules.
• 🟡 (15:57) Repository package-management convention: use Yarn classic 1.22.22 via Volta pinned in package.json; do not use npm. Commands: yarn install, yarn test, yarn test:watch, yarn test src/modules/__tests__/update-issue.js, yarn test -t "pattern", yarn lint, and yarn prettier.
• 🟡 (15:57) Single-test conventions: by file path yarn test src/modules/__tests__/update-issue.js; by test-name pattern yarn test -t "transformIssueBody"; combined yarn test src/modules/__tests__/update-issue.js -t "specific test name".
• 🟡 (15:57) Project structure: src/libs/ contains shared utilities and __tests__/; src/modules/ contains reusable core business logic and __tests__/; src/publish/ contains GitHub Actions entry points.
• 🟡 (15:57) Code-style conventions: filenames use kebab-case (examples details-from-context.js, update-issue.js); tests live in __tests__/ with the corresponding source filename; variables/functions use camelCase (examples detailsFromContext, publishRepo); constants/regex use UPPER_SNAKE_CASE (example TARGETS_SECTION_PARSER_REGEX).
• 🟡 (15:57) Module conventions: source files use CommonJS require/module.exports; test files use ES Modules import/export; import order is Node built-ins, external packages, then relative local modules. Named CommonJS exports are preferred for multiple exports; default module.exports = functionName is used for a single export.
• 🟡 (15:57) Formatting convention: Prettier defaults, double-quoted strings, required semicolons, and run yarn prettier before committing.
• 🟡 (15:57) Error-handling conventions: throw descriptive errors with context and potential remediation; validate inputs early with guard clauses (example error "Issue context is not defined" when context.payload.issue is absent); before reading files, check existence such as fs.existsSync(CRAFT_STATE_FILE_PATH) and return if absent.
• 🟡 (15:57) Testing conventions: Vitest v4.0.0 with globals enabled; describe, test, and expect need not be imported; mocks are auto-cleared between tests. Mock external dependencies with vi.mock(...), then require the module under test after mocks; inline snapshots may use toMatchInlineSnapshot.
• 🟡 (15:57) Key dependencies listed: @actions/core for GitHub Actions toolkit inputs/outputs/logging, @actions/github for the GitHub API client for Actions, and @sentry/node for Sentry error reporting.
• 🟡 (15:57) Common pattern documented: execute independent async operations in parallel with await Promise.all([operation1(), operation2()]);.