You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
ensure release.sh works with the latest on default branch (ensure no need to git pull locally before it runs) #336
The release already fetches current origin/main and creates its version bump there, independent of the checked-out branch and uncommitted work. What still comes from the local checkout is the running script, its summary prompt, and its summary helper.
Decision needed: Does “latest on default branch” mean the released source/version checks only (already implemented), or must the release tooling itself also run from the newly fetched revision? The latter needs a deliberate tooling handoff and regression coverage; do not close this as fully implemented without settling that distinction.
Activity
JacobStephens2 commentedon Oct 17, 2026
Triage Notes
The release already fetches current
origin/mainand creates its version bump there, independent of the checked-out branch and uncommitted work. What still comes from the local checkout is the running script, its summary prompt, and its summary helper.Decision needed: Does “latest on default branch” mean the released source/version checks only (already implemented), or must the release tooling itself also run from the newly fetched revision? The latter needs a deliberate tooling handoff and regression coverage; do not close this as fully implemented without settling that distinction.
JacobStephens2 commentedon Oct 25, 2026
Triage Notes
What we've established so far:
origin/mainin a temporary worktree.release-summary.md, andcargo runfor the summary and experiment) still runs from the local checkout.What we still need from you (@JacobStephens2):