Skip to content

ci: let the release gate pass on the commits since beta.3 - #109

Merged
arthware-dev merged 2 commits into
mainfrom
fix/release-gate-subjects
Sep 22, 2026
Merged

arthware-dev merged 2 commits into
mainfrom
fix/release-gate-subjects

Conversation

@arthware-dev

Copy link
Copy Markdown
Contributor

Summary

  • Stop counting the (#N) GitHub appends on squash against the 72-character subject limit. CI checks the title before the number exists, so two merged PRs passed CI and then failed the release gate.
  • Accept diary, capture and voice as component scopes (Memory Stacklet, Archivist Bot, AI Stacklet), which eight commits since v0.3.0-beta.3 already use.

tools/commit-lint --range v0.3.0-beta.3..HEAD goes from 11 failures to 1: 63e81e3, a refactor subject at 80 characters. Refactors are not in the changelog, so there is no entry to write by hand, and it drops out of the range at the next tag.

Two commits, meant to be merged with rebase.

CI checks a PR title before the squash merge appends " (#106)", so a
title that passed could land over 72 characters and then fail the
release gate. Two commits since the last tag did. The limit now
applies to the subject without the number GitHub adds.
Eight commits since the last tag use these scopes, and the release
gate rejected every one. Each names a component with an owner, like
`curator` and `wiki` already do: the diary renders as the Memory
Stacklet, capture as the Archivist Bot, voice as the AI Stacklet. The
scope table in the engineer guide lists them too.
@arthware-dev
arthware-dev merged commit 3b23e51 into main Sep 22, 2026
1 check passed
@arthware-dev
arthware-dev deleted the fix/release-gate-subjects branch September 22, 2026 08:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant