Distillation

Date: Aug 28, 2026

• 🟢 (11:29) Tool inspected docs/src/content/docs/targets/github.md: GitHub target creates releases and tags; if a Markdown changelog is present, it reads the release name and description from it.
• 🟢 (11:29) GitHub target configuration documented in docs/src/content/docs/targets/github.md: tagPrefix prefixes new git tags (empty default); previewReleases automatically detects/creates preview releases (default true); tagOnly creates only a tag without a GitHub release (default false); floatingTags creates/updates tags supporting {major}, {minor}, and {patch} placeholders. GITHUB_TOKEN is the required GitHub API-token environment variable.
• 🔴 (11:29) User asserted that floatingTags maintain latest-major-version tags that always point to the most recent release.
• 🟢 (11:29) Documentation example configures floatingTags as "v{major}" and "v{major}.{minor}"; for version 2.15.0, these create/update v2 and v2.15, respectively. This supports users pinning to a major version while automatically receiving updates.
• 🟢 (11:29) Documentation states tagPrefix supports independently versioned monorepo products by scoping tag writes and reads: latest-tag detection, changelog base, and CalVer scans all use the prefix. Example separate configurations use cli@ / mcp@ tag prefixes and matching release/cli / release/mcp branch prefixes; releasing 1.2.3 produces cli@1.2.3 / mcp@1.2.3 on release/cli/1.2.3 / release/mcp/1.2.3.
• 🟢 (11:29) Documentation defines top-level release workspaces: as independently versioned release units selected through --workspace <name> or CRAFT_WORKSPACE; example requires minVersion: 2.29.0, sets github.owner: getsentry, github.repo: toolkit, and defines cli / mcp workspaces with their respective release-branch and GitHub-target tag prefixes.
• 🟢 (11:29) Documentation states workspace names permit ASCII letters, digits, periods, underscores, and hyphens; they are not npm package workspaces. A workspace cannot use github.projectPath, and a workflow cannot provide both path and workspace; craft workspace list prints exact configured workspace names as a JSON array.
• 🟢 (11:29) Documentation cautions that multiple github targets with different tagPrefix values in one release unit are ambiguous: Craft uses the first prefix for read-path operations and logs a warning; separate release workspaces should be used for independent products.
• 🟢 (11:29) Documentation notes GitHub’s “Latest” badge is repository-wide, not tag-prefix-scoped. Craft’s isLatestRelease comparison is against the repository’s current latest release, so the badge can shift across monorepo products; tags, changelogs, release branches, and version detection remain per-product scoped.
• 🟢 (11:29) Documentation states when previewReleases: true (the default), releases with prerelease identifiers such as alpha, beta, or rc are marked as GitHub prereleases.