Skip to content

release v1.1.0 (sentinel re-fire) #39

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
EnriqueCanals merged 1 commit into from
Aug 16, 2026
Merged

release v1.1.0 (sentinel re-fire) #39

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions rfcs/2026-08-15_rename-to-dispatch.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,3 +58,12 @@ The golden test is updated first (TDD): it now generates with `name=dispatch` ex
- [x] (post-merge) GitHub repo renamed to `boldblackai/create-dispatch` (2026-08-15)
- [x] (post-merge) manual first publish of `@boldblackai/create-dispatch@1.1.0` (2026-08-15); `@boldblackai/create-bclaw` deprecated with a pointer to the new name
- [x] (post-merge) homepage DNS cutover to `dispatch.boldblack.ai` (live 2026-08-15)

## Implementation Notes

- The first release attempt (PR #38) was merged with a regular merge whose
commit message did not carry the `release v` prefix (the PR title was
truncated in the merge commit), so the `tag-on-merge.yml` sentinel never
fired and no `v1.1.0` tag was created. This release PR re-fires it;
release PRs must be **squash-merged** so the head commit message starts
with `release v`.