Distillation

Date: Sep 8, 2026

• 🔴 (16:17) User stated that floating tags always point to the most recent release.
• 🔴 (16:17) User stated that Action publish titles always carry the full concrete workspace path.
• 🟡 (16:17) Commit f174ceafa57355e71617f32ba1b0a030953be0a2 (test: describe workspace paths accurately, authored/committed Sep 8, 2026 16:02:39 UTC) renamed the src/__tests__/config.test.ts test from allows legacy workspace names to allows multi-segment workspace paths; it continues validating { workspaces: { 'cli/v2': {} } }.
• 🟡 (16:17) Documentation in docs/src/content/docs/targets/github.md defines floating tags as “latest major version” tags; floatingTags: ["v{major}", "v{major}.{minor}"] for version 2.15.0 creates v2 and v2.15, supporting consumers pinned to a major version while receiving updates.
• 🟡 (16:17) Documentation describes release workspaces as independently versioned release units under top-level workspaces:. Workspace keys may be literal paths or glob patterns, patterns expand to concrete directories relative to .craft.yml, and a concrete path must be selected using --workspace <path> or CRAFT_WORKSPACE.
• 🟡 (16:17) Documentation example uses minVersion: 2.29.0, top-level GitHub repository getsentry/toolkit, workspace glob packages/* with releaseBranchPrefix: release/cli and GitHub tagPrefix: "cli@", plus literal workspace tools/mcp with releaseBranchPrefix: release/mcp and GitHub tagPrefix: "mcp@".
• 🟡 (16:17) Documentation specifies workspace path segments must be nonempty ASCII segments composed of letters, digits, periods, underscores, and hyphens; segments cannot be ., .., __proto__, or begin with -.
• 🟡 (16:17) Documentation specifies that release workspaces are not npm package workspaces; Craft ignores files matched by configured workspace globs and rejects overlapping workspace keys.
• 🟡 (16:17) Documentation specifies a workspace cannot use github.projectPath, and a workflow cannot provide both path and workspace, to keep publish requests unambiguous.
• 🟡 (16:17) Documentation specifies craft workspace list prints concrete workspace paths as a JSON array for automation.
• 🟡 (16:17) 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.
• 🟡 (16:17) Documentation notes GitHub’s “Latest” badge is repository-wide rather than tag-prefix-scoped. isLatestRelease compares against the repository’s current latest release, so the badge can shift between monorepo products; tags, changelogs, release branches, and version detection remain per-product scoped.