Conversation
…publish scenario pass; user-visible release publication fix)
…h scenario pass; user-visible release publication fix)
…st fixture repair)
|
Single-maintainer release approval for v0.10.4 on 2026-04-25T15:24:45Z. Reviewed head SHA: ea16139 |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: ea161399db
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| if [[ "${current_branch}" == "${branch}" ]] || publish_pr_branch_exists "${resolved_workspace}" "${branch}"; then | ||
| publish_existing_commits=1 |
There was a problem hiding this comment.
Allowing publish_existing_commits=1 when any local branch exists (not just the current branch) lets repo-publish-pr.sh validate PR-parity against one tree and publish a different one: the wrapper computes parity from the currently checked-out workspace, then publish-pr can switch to another clean branch and push it. In practice, running the wrapper from main can still pass parity checks and publish an existing feature branch without proving parity for that branch’s tree, which violates the wrapper’s “tree being published” guarantee.
Useful? React with 👍 / 👎.
1 participant
Prepare Workcell v0.10.4 with release notes, refreshed upstream pins, and repo publication wrapper fixes.