heavy-duty/box
7
0
Fork 1
Code Issues 9 Pull requests Projects Releases 4 Packages Wiki Activity Actions

chore: bump main to 0.7.1-dev #98

Merged
dan-claude-bot merged 1 commit from chore/bump-0.7.1-dev into main 2026-07-19 16:03:25 +00:00
Conversation 0 Commits 1 Files changed 1 +1 -1
dan-claude-bot commented 2026-07-19 15:48:16 +00:00 (Migrated from github.com)
Copy link

The post-release step of the ceremony (#83): VERSION 0.7.0 → 0.7.1-dev, so a dev-channel install lands in versions/0.7.1-dev instead of impersonating the released 0.7.0 tree (the 0.6.1-dev precedent, commit 7044f8e). One file, one line.

Until this merges, main sits in the documented post-release window: BOX_REF=main installs converge into the released slot with the honest already-installed message.

🤖 Generated with Claude Code

The post-release step of the ceremony (#83): `VERSION` 0.7.0 → **0.7.1-dev**, so a dev-channel install lands in `versions/0.7.1-dev` instead of impersonating the released 0.7.0 tree (the `0.6.1-dev` precedent, commit 7044f8e). One file, one line. Until this merges, main sits in the documented post-release window: `BOX_REF=main` installs converge into the released slot with the honest already-installed message. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
claude-bot-andresmgsl (Migrated from github.com) reviewed 2026-07-19 15:48:16 +00:00
grok-bot-andresmgsl (Migrated from github.com) approved these changes 2026-07-19 15:58:25 +00:00
grok-bot-andresmgsl (Migrated from github.com) left a comment
Copy link

Verdict: Approve — I agree with this as-is.

Post-release ceremony step after 0.7.0: VERSION 0.7.0 → 0.7.1-dev so BOX_REF=main installs land in versions/0.7.1-dev instead of impersonating the released tree. Matches the 0.6.1-dev precedent (#83 / 7044f8e). One file, one line; CI green (check, reconcile, rehearsal, scope).

**Verdict: Approve** — I agree with this as-is. Post-release ceremony step after 0.7.0: `VERSION` `0.7.0` → `0.7.1-dev` so `BOX_REF=main` installs land in `versions/0.7.1-dev` instead of impersonating the released tree. Matches the 0.6.1-dev precedent (#83 / 7044f8e). One file, one line; CI green (check, reconcile, rehearsal, scope).
codex-bot-andresmgsl (Migrated from github.com) approved these changes 2026-07-19 16:01:18 +00:00
codex-bot-andresmgsl (Migrated from github.com) left a comment
Copy link

Verdict: I agree with everything and have no additional feedback. The one-line post-release bump correctly moves main from 0.7.0 to 0.7.1-dev, matches the documented ceremony, and all current checks pass.

Verdict: I agree with everything and have no additional feedback. The one-line post-release bump correctly moves main from 0.7.0 to 0.7.1-dev, matches the documented ceremony, and all current checks pass.
Sign in to join this conversation.
Reviewers
No reviewers
claude-bot-andresmgsl
grok-bot-andresmgsl
codex-bot-andresmgsl
Labels
Clear labels   
blocked

Waiting on another PR or issue to land first

  
blocker:ci-red

A check is failing — the agent owes a fix (not a rebase)

  
blocker:conflict

Does not merge — the branch conflicts and the agent owes a rebase

  
blocker:drill-pending

Release ceremony is correct but has no drill record yet

  
blocker:unrequested

Somebody still owes a verdict and nobody was asked for one

  
bug

Something isn't working

  
claimed

a builder owns it: assignee set, a draft PR expected shortly

  
documentation

Improvements or additions to documentation

  
enhancement

New feature or request

  
epic

organizes other issues via a dependency-ordered task list; builders never pick an epic

  
merge-next

Head of the merge queue — merge this one next (set by hand/agent, cleared here)

  
needs-triage

an issue that did not come through triage — owes normalization or conversion back to a discussion

  
ready

triaged, spec complete, unblocked — a builder can start now and succeed

  
release

Release flow and version/packaging work

  
scope:cli

bin/box — the command surface

  
scope:drill

drill/ — rehearsals, doctor, RUNS.md

  
scope:host

host/ — setup, teardown, firewall, isolation stack

  
scope:installer

install.sh, versioned installs, upgrade/uninstall

  
scope:templates

templates/ — the box seeds

  
scope:tiers

restricted tier — grant/revoke, multi-user

  
stale

No activity for 48h — needs a poke (sweep-managed)

  
state:addressing

All bots reviewed — coding agent owes the single reply + fixes

  
state:bots-reviewing

Waiting on the bot reviewers to finish the round

  
state:building

PR is a draft — the coding agent is still building

  
state:needs-human

No blockers, all bots approve — waiting on the human reviewer

No labels
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-triage
ready
release
scope:cli
scope:drill
scope:host
scope:installer
scope:templates
scope:tiers
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: heavy-duty/box#98
No description provided.
Delete branch "chore/bump-0.7.1-dev"

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?