Repository navigation
release(goal): prepare 1.3.50 stable with stale-write, completion proof and native OpenTUI 0.7 - #289
Merged
Merged
Conversation
…ed vs unresolved behavior
…2.1.4 native host
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![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: c6539e603e
ℹ️ 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".
…2.2 command conflict
…2.2 command conflict
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release candidate, not a claim of publication
After reviewed contributor #276 merged and exact-blob owner #288 verified 11/11 CI workflows, prepare @bybrawe/opencode-goal 1.3.50 (predecessor exactly 1.3.49). The new release includes #275 safe concurrent writers, #281 fail-closed artifact-backed completion, #283 exact 2.1.4 host canaries, #284 strict OpenTUI 0.5/0.7 peers; leaves unverified original field repro and silent provider/auth stalls open.
Files
package.jsonversion 1.3.50 with shippeddocs/releases/1.3.50.md.publish-npm.yml: exact version/predecessor guards 1.3.50/1.3.49; same immutable OIDC trusted publisher, exact-main 10 mandatory gates, no long-lived token, no added secret, no write contents. Update real publisher canary to actual tagged Loop v0.6.9 and OpenCode 2.1.4 rather than an old Loop source and 2.0.18.Conditions for merging a release-triggering PR
478c28aand Goalmainsource gates green; no new breaking report.gitHead, package exports, installer and consumer. A failed gate or failed npm publish means no claimed release.1.3.50really exists and install withnpx -y @bybrawe/opencode-goal@1.3.50from a clean consumer before marking stale_write aborts foreground chat when another Goal writer commits during chat.message #275 resolved. Windows Desktop GUI fix: close final Goal smoke-test edge cases #169, reporter's broad Field report: we are moving off /goal and /loop as our work driver - what we learned #279 and silent stalls P0: Surface silent compaction/auth pauses and long-running Goal stalls to the owning user (#279) #282 are not solved by this version.No Loop 0.6.10 release is included here; Loop's independently tested sidebar remains pending CLI auto-discovery (#191) and release gates (#192).