chore!: move to the umbra module path #63
No reviewers
Labels
No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
coilyco-flight-deck/mcp-beaver!63
Loading…
Reference in a new issue
No description provided.
Delete branch "chore/umbra-rename"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
cli-guardis nowforgejo.coilysiren.me/coilyco-flight-deck/umbra(umbra#285). The pin moves v0.131.0 -> v0.139.0 and the product name in prose follows. 23 files.Both packages this consumes survive the intervening cleanup (umbra#284 removed 20 dead packages):
http/opcoreandpkg/valuesource. Nothing else changed shape for us.Verified:
go build,go vetandgo test ./...all clean against v0.139.0.Left alone deliberately
github.com/coilysiren/cli-guardlinks stay as they are. I checked: the GitHub mirror still carries the old name and answers 200, while/umbra404s. Renaming those now would point the README at dead pages. They move once the mirror is renamed.Closing as already landed.
Every file this touches is byte-identical between
mainand this branch's head, andmain'sgo.modalready requiresforgejo.coilysiren.me/coilyco-flight-deck/umbra v0.139.0. Themain...headcompare shows zero commits ahead.The module path move is done. Branch left in place, so this is reopenable.