Distillation

Date: Sep 8, 2026

• 🟡 (10:11) src/modules/__tests__/details-from-context.js imports detailsFromContext and parsePublishTitle from ../details-from-context.js.
• 🟡 (10:11) detailsFromContext(inputsArgs) is tested with issue number: "223", title publish: getsentry/sentry@21.3.1, accepted label, Merge target: custom-branch, and checked targets github, npm[@sentry/node], and docker[latest]; expected result is { dry_run: "", merge_target: "custom-branch", path: ".", repo: "sentry", targets: ["github", "npm[@sentry/node]", "docker[latest]"], version: "21.3.1" }.
• 🟡 (10:11) detailsFromContext() is tested to preserve a + in version strings: title publish: getsentry/sentry-forked-django-stubs@4.2.6+sentry1 yields version: "4.2.6+sentry1".
• 🟡 (10:11) parsePublishTitle("publish: getsentry/sentry-javascript/packages/core@10.0.0") is expected to return { path: "/packages/core", repo: "sentry-javascript", version: "10.0.0" }; legacy/unqualified parsePublishTitle("publish: sentry-javascript@10.0.0") returns { path: undefined, repo: "sentry-javascript", version: "10.0.0" }.
• 🟡 (10:11) detailsFromContext(defaultTargetInputsArgs) treats Merge target: (default) as no merge target and returns { dry_run: "", merge_target: "", path: ".", repo: "sentry", targets: ["github", "docker[latest]"], version: "21.3.1" }.
• 🟡 (10:11) detailsFromContext({ context: {} }) is tested to reject with Error("Issue context is not defined") when the issue payload is missing.