release v1.1.0 - #38
Merged
Merged
Conversation
Marks the rename RFC Implemented: all post-merge service-side items landed 2026-08-15 (GitHub repo renamed to boldblackai/create-dispatch, manual first publish of @boldblackai/create-dispatch@1.1.0, old package deprecated with a pointer, homepage live at dispatch.boldblack.ai). Version 1.1.0 + changelog already on main from PR boldblackai#37. Co-Authored-By: Enrique Canals <84596+EnriqueCanals@users.noreply.github.com>
1 task
EnriqueCanals
added a commit
that referenced
this pull request
Aug 16, 2026
Re-fires the release sentinel: the previous release PR (#38) was merge-committed, so the head commit message did not start with 'release v' and tag-on-merge.yml skipped. Version 1.1.0 and the changelog are already on main; npm 1.1.0 is already published (manual first publish), so the workflow's publish step will detect and skip. Expected result: v1.1.0 tag + GitHub release. Co-authored-by: BoldBlackBot <296328274+BoldBlackBot@users.noreply.github.com> Co-authored-by: Enrique Canals <84596+EnriqueCanals@users.noreply.github.com>
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
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
Implemented— all post-merge service-side items are done: GitHub repo renamed toboldblackai/create-dispatch, manual first publish of@boldblackai/create-dispatch@1.1.0on npm,@boldblackai/create-bclawdeprecated with a pointer, homepage live atdispatch.boldblack.ai.What this merge triggers (by design)
The
release vcommit sentinel firestag-on-merge.ymlon push tomain: it tagsv1.1.0, extracts the changelog into a GitHub release, and runs the npm publish step — which will see 1.1.0 already published (manual first publish) and skip, exercising the trusted-publisher chain end-to-end. Please squash-merge this PR so the sentinel seesrelease v1.1.0 (#N)as the head commit message.Verification
Test plan
v1.1.0+ GitHub release appear; Actions run green with "Version 1.1.0 already published, skipping".