v0.1.0-alpha.9

Version v0.1.0-alpha.9 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Action pared down to three modes: release, status, check [ci]
  prerelease-label and git-sha inputs are removed from the action; those values now live in
  .changes/config.json branch config. CLI flags (--dry-run, --output, --notes,
  --prerelease-label, --git-sha) are scoped to the commands that use them instead of being
  global, so status and check show a clean help output.
• Branch config now controls release behaviour via a release enum [cli, ci]
  BranchConfig gains release (stable | prerelease | none), label, and sha fields.
  The old Prerelease bool is gone. release: none writes release.json without creating a
  git tag, enabling SHA-versioned develop builds (1.6.0-develop+gabc123) that publish to an
  API or artifact store without polluting the tag namespace.
• Optional category allowlist in config.json [cli]
  Set categories in .changes/config.json to restrict which category labels change files may use. Files declaring an unknown category fail validation. When the list is omitted, any category is accepted as before.
• PR check rejects change files with explicit pr: frontmatter [cli]
  Change files submitted in a PR must not set pr: to a number or null — the
  PR number is assigned automatically from git history at release time. Setting it
  manually in a PR could link the change to the wrong PR or suppress the link
  entirely. The check command now reports these as invalid.
• Releases record contributors [cli]
  When gh is available, release.json gains a contributors list of commit authors since the previous tag, and the generated notes get a Contributors footer that thanks them, excluding repo maintainers and bot accounts.
• Workflow dispatch accepts any prerelease label as free text [ci]
  The release workflow now takes a stable/prerelease mode toggle and a free-text label field (default: alpha), replacing the fixed dropdown of rc/alpha/beta options.
• init scaffolds config.json and GitHub Actions workflows [cli]
  init now creates .changes/config.json (with branch config derived from --branches) and
  both two-stage PR check workflows (.github/workflows/check-changes.yml and
  pr-check-comment.yml). Pass --action-ref to pin the action to a SHA. Use --no-workflows
  to skip workflow generation.
• Notice lines are now validated [cli]
  Notice levels must be info, warning, or error, and each line must follow the - level: message form. Invalid levels and malformed lines now fail validation instead of being silently dropped.
• Add a check command and branches config for pull request validation [ci]
  The new check command (and mode: check on the action) validates the change files a pull request adds and writes a verdict of ok, missing, or invalid. Release branches are declared in a branches map in .changes/config.json; a pull request whose base is not a release branch is skipped. The verdict is designed for a fork-safe two-stage workflow_run setup that posts the result as a sticky pull request comment.
• Two-stage workflow_run PR comment for change file check [ci]
  A fork-safe pull request comment workflow posts the change-file verdict as a sticky comment. Stage one (pr-check.yml) runs on pull_request with read-only permissions, executes the check command, and uploads the verdict JSON as an artifact. Stage two (pr-check-comment.yml) fires on workflow_run completion with pull-requests: write, downloads the artifact, and posts or updates the <!-- release-tool-check --> sticky comment on the PR.
• Change files can pin or suppress the PR number via frontmatter [cli]
  The pr: field is tri-state: omit it to derive the PR from git history (the existing behavior), set an integer to use it verbatim, or set pr: null to suppress the PR link entirely.
• Prereleases no longer consume change files or update the changelog [cli]
  The rc command now creates a lightweight tag from pending changes without touching .changes/ files or CHANGELOG.md. Only stable releases consume changes and write the changelog.
• release command auto-dispatches based on branch config [cli]
  The new release command reads .changes/config.json, resolves the current branch, and
  dispatches to stable or prerelease logic automatically. Manual rc and stable subcommands
  are removed; rc is replaced by prerelease for direct invocation. CI only ever needs to
  call release.
• Action gains a status mode [ci]
  The composite action now accepts mode: status, which validates pending change files and prints the next version without creating a tag. Useful as a pull request check.
• Fix subset reads skipping missing files and guard against path escapes [cli]
  Prerelease change gathering now correctly skips files that no longer exist instead of erroring, and subset file names are reduced to their basename so they cannot resolve outside .changes/.

v0.1.0-alpha.8

Version v0.1.0-alpha.8 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Action pared down to three modes: release, status, check [ci]
  prerelease-label and git-sha inputs are removed from the action; those values now live in
  .changes/config.json branch config. CLI flags (--dry-run, --output, --notes,
  --prerelease-label, --git-sha) are scoped to the commands that use them instead of being
  global, so status and check show a clean help output.
• Branch config now controls release behaviour via a release enum [cli, ci]
  BranchConfig gains release (stable | prerelease | none), label, and sha fields.
  The old Prerelease bool is gone. release: none writes release.json without creating a
  git tag, enabling SHA-versioned develop builds (1.6.0-develop+gabc123) that publish to an
  API or artifact store without polluting the tag namespace.
• Optional category allowlist in config.json [cli]
  Set categories in .changes/config.json to restrict which category labels change files may use. Files declaring an unknown category fail validation. When the list is omitted, any category is accepted as before.
• PR check rejects change files with explicit pr: frontmatter [cli]
  Change files submitted in a PR must not set pr: to a number or null — the
  PR number is assigned automatically from git history at release time. Setting it
  manually in a PR could link the change to the wrong PR or suppress the link
  entirely. The check command now reports these as invalid.
• Releases record contributors [cli]
  When gh is available, release.json gains a contributors list of commit authors since the previous tag, and the generated notes get a Contributors footer that thanks them, excluding repo maintainers and bot accounts.
• Workflow dispatch accepts any prerelease label as free text [ci]
  The release workflow now takes a stable/prerelease mode toggle and a free-text label field (default: alpha), replacing the fixed dropdown of rc/alpha/beta options.
• init scaffolds config.json and GitHub Actions workflows [cli]
  init now creates .changes/config.json (with branch config derived from --branches) and
  both two-stage PR check workflows (.github/workflows/check-changes.yml and
  pr-check-comment.yml). Pass --action-ref to pin the action to a SHA. Use --no-workflows
  to skip workflow generation.
• Notice lines are now validated [cli]
  Notice levels must be info, warning, or error, and each line must follow the - level: message form. Invalid levels and malformed lines now fail validation instead of being silently dropped.
• Add a check command and branches config for pull request validation [ci]
  The new check command (and mode: check on the action) validates the change files a pull request adds and writes a verdict of ok, missing, or invalid. Release branches are declared in a branches map in .changes/config.json; a pull request whose base is not a release branch is skipped. The verdict is designed for a fork-safe two-stage workflow_run setup that posts the result as a sticky pull request comment.
• Two-stage workflow_run PR comment for change file check [ci]
  A fork-safe pull request comment workflow posts the change-file verdict as a sticky comment. Stage one (pr-check.yml) runs on pull_request with read-only permissions, executes the check command, and uploads the verdict JSON as an artifact. Stage two (pr-check-comment.yml) fires on workflow_run completion with pull-requests: write, downloads the artifact, and posts or updates the <!-- release-tool-check --> sticky comment on the PR.
• Change files can pin or suppress the PR number via frontmatter [cli]
  The pr: field is tri-state: omit it to derive the PR from git history (the existing behavior), set an integer to use it verbatim, or set pr: null to suppress the PR link entirely.
• Prereleases no longer consume change files or update the changelog [cli]
  The rc command now creates a lightweight tag from pending changes without touching .changes/ files or CHANGELOG.md. Only stable releases consume changes and write the changelog.
• release command auto-dispatches based on branch config [cli]
  The new release command reads .changes/config.json, resolves the current branch, and
  dispatches to stable or prerelease logic automatically. Manual rc and stable subcommands
  are removed; rc is replaced by prerelease for direct invocation. CI only ever needs to
  call release.
• Action gains a status mode [ci]
  The composite action now accepts mode: status, which validates pending change files and prints the next version without creating a tag. Useful as a pull request check.
• Fix subset reads skipping missing files and guard against path escapes [cli]
  Prerelease change gathering now correctly skips files that no longer exist instead of erroring, and subset file names are reduced to their basename so they cannot resolve outside .changes/.

v0.1.0-alpha.7

Version v0.1.0-alpha.7 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Action pared down to three modes: release, status, check [ci]
  prerelease-label and git-sha inputs are removed from the action; those values now live in
  .changes/config.json branch config. CLI flags (--dry-run, --output, --notes,
  --prerelease-label, --git-sha) are scoped to the commands that use them instead of being
  global, so status and check show a clean help output.
• Branch config now controls release behaviour via a release enum [cli, ci]
  BranchConfig gains release (stable | prerelease | none), label, and sha fields.
  The old Prerelease bool is gone. release: none writes release.json without creating a
  git tag, enabling SHA-versioned develop builds (1.6.0-develop+gabc123) that publish to an
  API or artifact store without polluting the tag namespace.
• Optional category allowlist in config.json [cli]
  Set categories in .changes/config.json to restrict which category labels change files may use. Files declaring an unknown category fail validation. When the list is omitted, any category is accepted as before.
• PR check rejects change files with explicit pr: frontmatter [cli]
  Change files submitted in a PR must not set pr: to a number or null — the
  PR number is assigned automatically from git history at release time. Setting it
  manually in a PR could link the change to the wrong PR or suppress the link
  entirely. The check command now reports these as invalid.
• Releases record contributors [cli]
  When gh is available, release.json gains a contributors list of commit authors since the previous tag, and the generated notes get a Contributors footer that thanks them, excluding repo maintainers and bot accounts.
• Workflow dispatch accepts any prerelease label as free text [ci]
  The release workflow now takes a stable/prerelease mode toggle and a free-text label field (default: alpha), replacing the fixed dropdown of rc/alpha/beta options.
• init scaffolds config.json and GitHub Actions workflows [cli]
  init now creates .changes/config.json (with branch config derived from --branches) and
  both two-stage PR check workflows (.github/workflows/check-changes.yml and
  pr-check-comment.yml). Pass --action-ref to pin the action to a SHA. Use --no-workflows
  to skip workflow generation.
• Notice lines are now validated [cli]
  Notice levels must be info, warning, or error, and each line must follow the - level: message form. Invalid levels and malformed lines now fail validation instead of being silently dropped.
• Add a check command and branches config for pull request validation [ci]
  The new check command (and mode: check on the action) validates the change files a pull request adds and writes a verdict of ok, missing, or invalid. Release branches are declared in a branches map in .changes/config.json; a pull request whose base is not a release branch is skipped. The verdict is designed for a fork-safe two-stage workflow_run setup that posts the result as a sticky pull request comment.
• Two-stage workflow_run PR comment for change file check [ci]
  A fork-safe pull request comment workflow posts the change-file verdict as a sticky comment. Stage one (pr-check.yml) runs on pull_request with read-only permissions, executes the check command, and uploads the verdict JSON as an artifact. Stage two (pr-check-comment.yml) fires on workflow_run completion with pull-requests: write, downloads the artifact, and posts or updates the <!-- release-tool-check --> sticky comment on the PR.
• Change files can pin or suppress the PR number via frontmatter [cli]
  The pr: field is tri-state: omit it to derive the PR from git history (the existing behavior), set an integer to use it verbatim, or set pr: null to suppress the PR link entirely.
• Prereleases no longer consume change files or update the changelog [cli]
  The rc command now creates a lightweight tag from pending changes without touching .changes/ files or CHANGELOG.md. Only stable releases consume changes and write the changelog.
• release command auto-dispatches based on branch config [cli]
  The new release command reads .changes/config.json, resolves the current branch, and
  dispatches to stable or prerelease logic automatically. Manual rc and stable subcommands
  are removed; rc is replaced by prerelease for direct invocation. CI only ever needs to
  call release.
• Action gains a status mode [ci]
  The composite action now accepts mode: status, which validates pending change files and prints the next version without creating a tag. Useful as a pull request check.
• Fix subset reads skipping missing files and guard against path escapes [cli]
  Prerelease change gathering now correctly skips files that no longer exist instead of erroring, and subset file names are reduced to their basename so they cannot resolve outside .changes/.

v0.1.0-alpha.6

Version v0.1.0-alpha.6 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Action pared down to three modes: release, status, check [ci]
  prerelease-label and git-sha inputs are removed from the action; those values now live in
  .changes/config.json branch config. CLI flags (--dry-run, --output, --notes,
  --prerelease-label, --git-sha) are scoped to the commands that use them instead of being
  global, so status and check show a clean help output.
• Branch config now controls release behaviour via a release enum [cli, ci]
  BranchConfig gains release (stable | prerelease | none), label, and sha fields.
  The old Prerelease bool is gone. release: none writes release.json without creating a
  git tag, enabling SHA-versioned develop builds (1.6.0-develop+gabc123) that publish to an
  API or artifact store without polluting the tag namespace.
• Optional category allowlist in config.json [cli]
  Set categories in .changes/config.json to restrict which category labels change files may use. Files declaring an unknown category fail validation. When the list is omitted, any category is accepted as before.
• Releases record contributors [cli]
  When gh is available, release.json gains a contributors list of commit authors since the previous tag, and the generated notes get a Contributors footer that thanks them, excluding repo maintainers and bot accounts.
• Workflow dispatch accepts any prerelease label as free text [ci]
  The release workflow now takes a stable/prerelease mode toggle and a free-text label field (default: alpha), replacing the fixed dropdown of rc/alpha/beta options.
• init scaffolds config.json and GitHub Actions workflows [cli]
  init now creates .changes/config.json (with branch config derived from --branches) and
  both two-stage PR check workflows (.github/workflows/check-changes.yml and
  pr-check-comment.yml). Pass --action-ref to pin the action to a SHA. Use --no-workflows
  to skip workflow generation.
• Notice lines are now validated [cli]
  Notice levels must be info, warning, or error, and each line must follow the - level: message form. Invalid levels and malformed lines now fail validation instead of being silently dropped.
• Add a check command and branches config for pull request validation [ci]
  The new check command (and mode: check on the action) validates the change files a pull request adds and writes a verdict of ok, missing, or invalid. Release branches are declared in a branches map in .changes/config.json; a pull request whose base is not a release branch is skipped. The verdict is designed for a fork-safe two-stage workflow_run setup that posts the result as a sticky pull request comment.
• Two-stage workflow_run PR comment for change file check [ci]
  A fork-safe pull request comment workflow posts the change-file verdict as a sticky comment. Stage one (pr-check.yml) runs on pull_request with read-only permissions, executes the check command, and uploads the verdict JSON as an artifact. Stage two (pr-check-comment.yml) fires on workflow_run completion with pull-requests: write, downloads the artifact, and posts or updates the <!-- release-tool-check --> sticky comment on the PR.
• Change files can pin or suppress the PR number via frontmatter [cli]
  The pr: field is tri-state: omit it to derive the PR from git history (the existing behavior), set an integer to use it verbatim, or set pr: null to suppress the PR link entirely.
• Prereleases no longer consume change files or update the changelog [cli]
  The rc command now creates a lightweight tag from pending changes without touching .changes/ files or CHANGELOG.md. Only stable releases consume changes and write the changelog.
• release command auto-dispatches based on branch config [cli]
  The new release command reads .changes/config.json, resolves the current branch, and
  dispatches to stable or prerelease logic automatically. Manual rc and stable subcommands
  are removed; rc is replaced by prerelease for direct invocation. CI only ever needs to
  call release.
• Action gains a status mode [ci]
  The composite action now accepts mode: status, which validates pending change files and prints the next version without creating a tag. Useful as a pull request check.
• Fix subset reads skipping missing files and guard against path escapes [cli]
  Prerelease change gathering now correctly skips files that no longer exist instead of erroring, and subset file names are reduced to their basename so they cannot resolve outside .changes/.

v0.1.0-alpha.5

Version v0.1.0-alpha.5 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Action pared down to three modes: release, status, check [ci]
  prerelease-label and git-sha inputs are removed from the action; those values now live in
  .changes/config.json branch config. CLI flags (--dry-run, --output, --notes,
  --prerelease-label, --git-sha) are scoped to the commands that use them instead of being
  global, so status and check show a clean help output.
• Branch config now controls release behaviour via a release enum [cli, ci]
  BranchConfig gains release (stable | prerelease | none), label, and sha fields.
  The old Prerelease bool is gone. release: none writes release.json without creating a
  git tag, enabling SHA-versioned develop builds (1.6.0-develop+gabc123) that publish to an
  API or artifact store without polluting the tag namespace.
• Optional category allowlist in config.json [cli]
  Set categories in .changes/config.json to restrict which category labels change files may use. Files declaring an unknown category fail validation. When the list is omitted, any category is accepted as before.
• Releases record contributors [cli]
  When gh is available, release.json gains a contributors list of commit authors since the previous tag, and the generated notes get a Contributors footer that thanks them, excluding repo maintainers and bot accounts.
• Workflow dispatch accepts any prerelease label as free text [ci]
  The release workflow now takes a stable/prerelease mode toggle and a free-text label field (default: alpha), replacing the fixed dropdown of rc/alpha/beta options.
• init scaffolds config.json and GitHub Actions workflows [cli]
  init now creates .changes/config.json (with branch config derived from --branches) and
  both two-stage PR check workflows (.github/workflows/check-changes.yml and
  pr-check-comment.yml). Pass --action-ref to pin the action to a SHA. Use --no-workflows
  to skip workflow generation.
• Notice lines are now validated [cli]
  Notice levels must be info, warning, or error, and each line must follow the - level: message form. Invalid levels and malformed lines now fail validation instead of being silently dropped.
• Add a check command and branches config for pull request validation [ci]
  The new check command (and mode: check on the action) validates the change files a pull request adds and writes a verdict of ok, missing, or invalid. Release branches are declared in a branches map in .changes/config.json; a pull request whose base is not a release branch is skipped. The verdict is designed for a fork-safe two-stage workflow_run setup that posts the result as a sticky pull request comment.
• Two-stage workflow_run PR comment for change file check [ci]
  A fork-safe pull request comment workflow posts the change-file verdict as a sticky comment. Stage one (pr-check.yml) runs on pull_request with read-only permissions, executes the check command, and uploads the verdict JSON as an artifact. Stage two (pr-check-comment.yml) fires on workflow_run completion with pull-requests: write, downloads the artifact, and posts or updates the <!-- release-tool-check --> sticky comment on the PR.
• Change files can pin or suppress the PR number via frontmatter [cli]
  The pr: field is tri-state: omit it to derive the PR from git history (the existing behavior), set an integer to use it verbatim, or set pr: null to suppress the PR link entirely.
• Prereleases no longer consume change files or update the changelog [cli]
  The rc command now creates a lightweight tag from pending changes without touching .changes/ files or CHANGELOG.md. Only stable releases consume changes and write the changelog.
• release command auto-dispatches based on branch config [cli]
  The new release command reads .changes/config.json, resolves the current branch, and
  dispatches to stable or prerelease logic automatically. Manual rc and stable subcommands
  are removed; rc is replaced by prerelease for direct invocation. CI only ever needs to
  call release.
• Action gains a status mode [ci]
  The composite action now accepts mode: status, which validates pending change files and prints the next version without creating a tag. Useful as a pull request check.
• Fix subset reads skipping missing files and guard against path escapes [cli]
  Prerelease change gathering now correctly skips files that no longer exist instead of erroring, and subset file names are reduced to their basename so they cannot resolve outside .changes/.

v0.1.0-alpha.4

Version v0.1.0-alpha.4 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Optional category allowlist in config.json [cli]
  Set categories in .changes/config.json to restrict which category labels change files may use. Files declaring an unknown category fail validation. When the list is omitted, any category is accepted as before.
• Releases record contributors [cli]
  When gh is available, release.json gains a contributors list of commit authors since the previous tag, and the generated notes get a Contributors footer that thanks them, excluding repo maintainers and bot accounts.
• Workflow dispatch accepts any prerelease label as free text [ci]
  The release workflow now takes a stable/prerelease mode toggle and a free-text label field (default: alpha), replacing the fixed dropdown of rc/alpha/beta options.
• Notice lines are now validated [cli]
  Notice levels must be info, warning, or error, and each line must follow the - level: message form. Invalid levels and malformed lines now fail validation instead of being silently dropped.
• Add a check command and branches config for pull request validation [ci]
  The new check command (and mode: check on the action) validates the change files a pull request adds and writes a verdict of ok, missing, or invalid. Release branches are declared in a branches map in .changes/config.json; a pull request whose base is not a release branch is skipped. The verdict is designed for a fork-safe two-stage workflow_run setup that posts the result as a sticky pull request comment.
• Two-stage workflow_run PR comment for change file check [ci]
  A fork-safe pull request comment workflow posts the change-file verdict as a sticky comment. Stage one (pr-check.yml) runs on pull_request with read-only permissions, executes the check command, and uploads the verdict JSON as an artifact. Stage two (pr-check-comment.yml) fires on workflow_run completion with pull-requests: write, downloads the artifact, and posts or updates the <!-- release-tool-check --> sticky comment on the PR.
• Change files can pin or suppress the PR number via frontmatter [cli]
  The pr: field is tri-state: omit it to derive the PR from git history (the existing behavior), set an integer to use it verbatim, or set pr: null to suppress the PR link entirely.
• Prereleases no longer consume change files or update the changelog [cli]
  The rc command now creates a lightweight tag from pending changes without touching .changes/ files or CHANGELOG.md. Only stable releases consume changes and write the changelog.
• Action gains a status mode [ci]
  The composite action now accepts mode: status, which validates pending change files and prints the next version without creating a tag. Useful as a pull request check.
• Fix subset reads skipping missing files and guard against path escapes [cli]
  Prerelease change gathering now correctly skips files that no longer exist instead of erroring, and subset file names are reduced to their basename so they cannot resolve outside .changes/.

v0.1.0-alpha.11

Version v0.1.0-alpha.11 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Action pared down to three modes: release, status, check [ci]
• Branch config now controls release behaviour via a release enum [cli, ci]
• Optional category allowlist in config.json [cli]
• Changelog entries show title only; release note gains title and body [cli]
• PR check rejects change files with explicit pr: frontmatter [cli]
• Releases record contributors [cli]
• Workflow dispatch accepts any prerelease label as free text [ci]
• init scaffolds config.json and GitHub Actions workflows [cli]
• Notice lines are now validated [cli]
• Add a check command and branches config for pull request validation [ci]
• Two-stage workflow_run PR comment for change file check [ci]
• Change files can pin or suppress the PR number via frontmatter [cli]
• Prereleases no longer consume change files or update the changelog [cli]
• release command auto-dispatches based on branch config [cli]
• Action gains a status mode [ci]
• Fix subset reads skipping missing files and guard against path escapes [cli]

v0.1.0-alpha.10

Version v0.1.0-alpha.10 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Action pared down to three modes: release, status, check [ci]
• Branch config now controls release behaviour via a release enum [cli, ci]
• Optional category allowlist in config.json [cli]
• Changelog entries show title only; release note gains title and body [cli]
• PR check rejects change files with explicit pr: frontmatter [cli]
• Releases record contributors [cli]
• Workflow dispatch accepts any prerelease label as free text [ci]
• init scaffolds config.json and GitHub Actions workflows [cli]
• Notice lines are now validated [cli]
• Add a check command and branches config for pull request validation [ci]
• Two-stage workflow_run PR comment for change file check [ci]
• Change files can pin or suppress the PR number via frontmatter [cli]
• Prereleases no longer consume change files or update the changelog [cli]
• release command auto-dispatches based on branch config [cli]
• Action gains a status mode [ci]
• Fix subset reads skipping missing files and guard against path escapes [cli]

v0.1.0-alpha.3

Version v0.1.0-alpha.3 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Optional category allowlist in config.json [cli]
  Set categories in .changes/config.json to restrict which category labels change files may use. Files declaring an unknown category fail validation. When the list is omitted, any category is accepted as before.
• Releases record contributors [cli]
  When gh is available, release.json gains a contributors list of commit authors since the previous tag, and the generated notes get a Contributors footer that thanks them, excluding repo maintainers and bot accounts.
• Workflow dispatch accepts any prerelease label as free text [ci]
  The release workflow now takes a stable/prerelease mode toggle and a free-text label field (default: alpha), replacing the fixed dropdown of rc/alpha/beta options.
• Notice lines are now validated [cli]
  Notice levels must be info, warning, or error, and each line must follow the - level: message form. Invalid levels and malformed lines now fail validation instead of being silently dropped.
• Change files can pin or suppress the PR number via frontmatter [cli]
  The pr: field is tri-state: omit it to derive the PR from git history (the existing behavior), set an integer to use it verbatim, or set pr: null to suppress the PR link entirely.
• Prereleases no longer consume change files or update the changelog [cli]
  The rc command now creates a lightweight tag from pending changes without touching .changes/ files or CHANGELOG.md. Only stable releases consume changes and write the changelog.
• Action gains a status mode [ci]
  The composite action now accepts mode: status, which validates pending change files and prints the next version without creating a tag. Useful as a pull request check.
• Fix subset reads skipping missing files and guard against path escapes [cli]
  Prerelease change gathering now correctly skips files that no longer exist instead of erroring, and subset file names are reduced to their basename so they cannot resolve outside .changes/.

v0.1.0-alpha.2

Version v0.1.0-alpha.2 Release Notes

Prerelease flow overhaul: lightweight tags, flexible labels.

• Workflow dispatch accepts any prerelease label as free text [ci]
  The release workflow now takes a stable/prerelease mode toggle and a free-text label field (default: alpha), replacing the fixed dropdown of rc/alpha/beta options.
• Prereleases no longer consume change files or update the changelog [cli]
  The rc command now creates a lightweight tag from pending changes without touching .changes/ files or CHANGELOG.md. Only stable releases consume changes and write the changelog.