DX-2192: create GitHub release as a draft for human review#48
Open
lloyd-cio wants to merge 1 commit into
Open
Conversation
lloyd-cio
marked this pull request as draft
June 17, 2026 16:55
lloyd-cio
force-pushed
the
release-notes-from-export
branch
from
June 22, 2026 23:51
d39b170 to
0738c1b
Compare
lloyd-cio
changed the title
Narrows this PR to just the draft-release gate. The export-commit marker machinery (build-release-notes / extractNotesBlock and the release.yml wiring) is dropped as redundant: release notes are handled by the maintainer skill (cio-cli#125), which reads source PR titles directly. The draft release is the human review point before Publish. DX-2192
lloyd-cio
force-pushed
the
release-notes-from-export
branch
from
June 23, 2026 22:38
0738c1b to
a69bec6
Compare
lloyd-cio
marked this pull request as ready for review
June 23, 2026 22:38
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.
Narrowed to the draft-release gate only.
.goreleaser.yamlnow setsrelease.draft: true, so GoReleaser creates the GitHub release as a draft. Artifacts (npm + GitHub Packages) still build and upload automatically; the human gate is on the release page, which a maintainer reviews and clicks Publish.Dropped from the original PR: the export-commit marker machinery (
build-release-notes/extractNotesBlockin release-workflow.js, therelease.ymlwiring, and the unit tests). That path is redundant: release notes are handled by the maintainer skill in cio-cli#125, which reads source PR titles directly. cio-cli#123 (which embedded the markers) is closed.Pairs with: cli#47 (manual merge trigger), cio-cli#125 (release-notes skill).
Linear: DX-2192