Distillation

Date: Aug 28, 2026

• 🔴 (18:47) User-provided repository guidance: Publish is a pure CommonJS JavaScript project on Node.js 24.0.0; use Yarn classic 1.22.22 via Volta and do not use npm.
• 🔴 (18:47) User-provided repository guidance: run all tests with yarn test; a single file with yarn test src/modules/__tests__/update-issue.js; test-name pattern with yarn test -t "pattern"; combined file/pattern with yarn test src/modules/__tests__/update-issue.js -t "specific test name"; lint with yarn lint; format with yarn prettier.
• 🔴 (18:47) User-provided repository conventions: source is organized as src/libs/ shared utilities, src/modules/ reusable core business logic, and src/publish/ GitHub Actions workflow entry points; files use kebab-case; colocated tests reside in __tests__/ and share the source filename.
• 🔴 (18:47) User-provided repository conventions: variables/functions use camelCase; constants/regex patterns use UPPER_SNAKE_CASE; source files use CommonJS (require/module.exports), test files use ES Modules (import/export); import order is Node.js built-ins, external packages, then local relative modules.
• 🔴 (18:47) User-provided repository conventions: use Prettier defaults, double-quoted strings, required semicolons, and run yarn prettier before committing; named CommonJS exports are preferred for multiple exports.
• 🔴 (18:47) User-provided error-handling preference: throw descriptive errors with context and potential remedies; validate early with guard clauses; always throw for unexpected switch values, e.g. default: throw new Error(\Unknown status: '${status}'`);; check file existence with fs.existsSync(CRAFT_STATE_FILE_PATH)` before reading files.
• 🔴 (18:47) User-provided testing conventions: Vitest v4.0.0 with globals enabled and auto-cleared mocks; mock external dependencies with vi.mock(...); import the module under test after mocks; inline snapshots may be used for complex output.
• 🔴 (18:47) User-provided project context: key dependencies are @actions/core, @actions/github, and @sentry/node; src/publish/ entry points are invoked by GitHub Actions workflows, using issue-based workflows triggered by labels and comments; all code is owned by @getsentry/releng (Release Engineering).