Dashboard › craft › Distillation
b277130d-3888-4323-94b3-0e6c18c2feb2["lore_tm_v1_9TFJilTHgkyIZI8H90-ptYtdz0NQC87nRl934YbPCME","lore_tm_v1_68KVQeDAipx3Zfqrt-2Oag8USW9hAM7IYdipJw-PBeg"]
Date: Sep 3, 2026
minVersion side.action.yml Request publish step constructs issue titles as publish: ${GITHUB_REPOSITORY}${SUBDIRECTORY}${WORKSPACE:+/$WORKSPACE}@${RESOLVED_VERSION}; it receives WORKSPACE: ${{ inputs.workspace }}, so a workspace is appended after SUBDIRECTORY.action.yml Request publish step uses CHANGELOG_FILE rather than an environment-variable changelog to avoid Linux ARG_MAX/E2BIG failures for changelogs exceeding approximately 2 MB; it reads the file when available, caps issue-body changelog content at MAX_CHANGELOG_CHARS=60000, and appends --- plus *Changelog truncated for issue body.* when truncated to fit GitHub’s approximately 65,536-character body limit.action.yml publish request deduplication lists open issues with gh -R "$PUBLISH_REPO" issue list --json title,url,number,body, filters for an exact title using jq, and takes the first match because issue listing is newest-first; this avoids GitHub Search API indexing delays and query-syntax edge cases.action.yml preserves checked publish targets when refreshing an existing issue: it extracts checked [x]/[X] targets only from the markdown section between ### Targets and Checked targets will be skipped, stores names in associative array checked_targets, and marks matching new target lines [x].action.yml updates an existing publish issue body via gh issue edit "$existing_issue_number" -R "$PUBLISH_REPO" --body "$body"; on permission failure it warns and retains the existing issue as-is. Otherwise it creates an issue with gh issue create -R "$PUBLISH_REPO" --title "$title" --body "$body".src/config.ts compatibility logic comment states it relaxes only the current-version side: // We only relax the CURRENT side (never the configured minVersion side).; it defines effectiveCurrentVersion: SemVer = currentVersion.pre ....