Skip to content

release v1.1.0 - #38

Merged
EnriqueCanals merged 1 commit into
boldblackai:mainfrom
BoldBlackBot:release/v1.1.0
Aug 16, 2026
Merged

release v1.1.0#38
EnriqueCanals merged 1 commit into
boldblackai:mainfrom
BoldBlackBot:release/v1.1.0

Conversation

@BoldBlackBot

Copy link
Copy Markdown
Contributor

Summary

  • Release cut for v1.1.0 (the dispatch rename, merged in feat: rename bclaw to dispatch (package, repo identity, template, v1.1.0) #37).
  • Marks the rename RFC Implemented — all post-merge service-side items are done: GitHub repo renamed to boldblackai/create-dispatch, manual first publish of @boldblackai/create-dispatch@1.1.0 on npm, @boldblackai/create-bclaw deprecated with a pointer, homepage live at dispatch.boldblack.ai.

What this merge triggers (by design)

The release v commit sentinel fires tag-on-merge.yml on push to main: it tags v1.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 sees release v1.1.0 (#N) as the head commit message.

Verification

  • Only file changed: RFC status + checklist boxes (content-only diff, no code).
  • Version + changelog already verified on main (1.1.0).

Test plan

  • After merge: confirm tag v1.1.0 + GitHub release appear; Actions run green with "Version 1.1.0 already published, skipping".

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>
@EnriqueCanals
EnriqueCanals merged commit 1507a66 into boldblackai:main Aug 16, 2026
1 check passed
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>
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.

2 participants