Conversation
…(Event 75) CP-RELEASE-PLEASE-CHKPT-FILTER-01 (v1.0.1 polish mini-batch CP #1). Two release-please workflow runs failed 2026-04-27 with GraphQL 500 on chkpt: commit 0f66bd0 in master history. The chkpt: prefix is not a Conventional Commits type; release-please's parser surfaced a 500 when walking merge-commit history that contained it. Fix: declare changelog-sections explicitly, including chkpt as a hidden type. release-please now recognizes chkpt: as valid and skips it cleanly without emitting a changelog entry. Standard CC types preserved with default visibility (feat / fix / perf / deps / revert visible; docs / style / chore / refactor / test / build / ci hidden — same as release-please default behavior). NOT BLOCKING v1.0.0 GA — manual tag cut already shipped (Event 72). This unblocks the release-please auto-PR for the next version cycle. If this config-only fix doesn't resolve the workflow failure on next push, escalate to Path 2: fix the chkpt-hook footgun directly in core/hooks/checkpoint.py to use Conventional Commits-compatible prefix (e.g., chore(chkpt):). Cross-references Events 57, 61, 70 (chkpt-hook race-with-operator-commit footgun history). Effort: ~30 min (Path 1 config-only). Soak-safe (CI config only; post-soak anyway). First v1.0.1 polish CP shipped.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
First v1.0.1 polish mini-batch CP shipped — fixes the recurring
release-pleaseworkflow failure onchkpt:commits.Trigger. Two
release-pleaseworkflow runs failed 2026-04-27 (request7411:35550C:15F898F:55C5B22:69EF9AA0+ retryE451:4925:9B0436:26E3C3A:69EF9DA8) with the same GraphQL 500-class error wrapping a parser issue on commit0f66bd0(titlechkpt: 2026-04-27T02:10:02, auto-generated bycore/hooks/checkpoint.py). Thechkpt:prefix is not a Conventional Commits type, so release-please's parser choked when walking merge-commit history.What this changes
release-please-config.json: addschangelog-sectionsarray to the package config, declaring all standard Conventional Commits types explicitly + addingchkptas a hidden type so the parser recognizes and skips it cleanly without emitting a changelog entry.Behavior matches release-please default for the standard 12 types;
chkptis the only addition.What this is not
This is Path 1 (config-only) from the CP description. It does NOT fix the
chkpt:hook footgun at the source. The recurring chkpt-hook race-with-operator-commit footgun (Events 57, 61, 70) remains; this just stops downstream CI breakage.If after merge release-please STILL fails on the next master push, escalate to Path 2: modify
core/hooks/checkpoint.pyto emit a Conventional Commits-compatible prefix (e.g.,chore(chkpt):). That's larger scope (touchescore/hooks/) and would land as a separate v1.0.1 polish CP.Verification
python3 -m json.tool release-please-config.jsonpasses (JSON valid)changelog-sectionsschema matches release-please-action@v4 documented format (type+section+ optionalhidden)kernel/FALSIFIABILITY_CONDITIONS.mdaction-on-disconfirmation policy). If it fails, fall back to Path 2.Soak-invariant
Zero
kernel/*/core/hooks/*/core/blueprints/*/src/episteme/*/tests/*/templates/*/labs/*touches. Single-file CI config edit. (Soak window already closed via Event 72; called out for completeness.)v1.0.1 polish queue status
CP-RELEASE-PLEASE-CHKPT-FILTER-01 (this PR — Event 75) is CP #1 of 4 in
~/episteme-private/docs/cp-v1.0.1-polish.md. Remaining:episteme profile audit ackCLI)Cross-references
~/episteme-private/docs/cp-v1.0.1-polish.md§ CP-RELEASE-PLEASE-CHKPT-FILTER-01~/episteme-private/docs/PROGRESS.mdEvent 75 entry (private)