release: prepare v1.7.3#91
Conversation
Why: - the installed Codex CLI is 0.139.0 while SwiftASB still documented and enforced a 0.138.x reviewed window - the promoted v0.139.0 wire delta is intentionally small and keeps the new MCP status thread target internal-only for now Verification: - swift build - swift test - bash scripts/repo-maintenance/validate-all.sh - uv run pytest - git diff --check
|
Warning Review limit reached
More reviews will be available in 50 minutes and 1 second. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughSwiftASB v1.7.3 patch release: bumps ChangesSwiftASB v1.7.3: Codex CLI 0.139.x compatibility and threadId internalization
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Possibly related PRs
Suggested labels
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![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: 47ba5eb7bb
ℹ️ 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".
| - 2026-06-09: Published `v1.7.3` with the ASBPresentation foundation, first | ||
| ASBAppKit thread sidebar view, Codex CLI `0.138.x` generated-wire refresh, | ||
| and PolyForm Noncommercial license transition. | ||
| - 2026-06-09: Prepared the `v1.7.2` release branch with the ASBPresentation | ||
| - 2026-06-09: Prepared the `v1.7.3` release branch with the ASBPresentation |
There was a problem hiding this comment.
These June 9 history entries describe the prior ASBPresentation/ASBAppKit and Codex CLI 0.138.x release, so changing them to v1.7.3 makes the roadmap claim that v1.7.3 was already published/prepared before the new June 13 v1.7.3 entry. This will mislead release audits; keep these historical entries on the version that actually shipped that work (v1.7.2).
Useful? React with 👍 / 👎.
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@docs/agents/reports/2026-06-11-agentsb-schema-review.md`:
- Around line 48-54: The report file contains sensitive machine-local
information that should not be committed. In the Repository root field (line
48), replace the absolute path `/Users/galew/.codex/worktrees/8d09/SwiftASB`
with a repo-relative path like `.` or `./` to indicate the repository root, or
omit this field entirely. Additionally, remove or redact the Git dirty state
field on line 50 as it represents environment-specific state that is not
relevant to a committed report. Keep only the necessary metadata that documents
the review context without exposing user-specific paths or local machine state.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 022ddfe2-1213-445c-ba30-ca2f49d21ff0
⛔ Files ignored due to path filters (1)
Sources/SwiftASB/Generated/CodexWire/Latest/CodexLifecycleV2Batch+JSONValue.swiftis excluded by!**/generated/**
📒 Files selected for processing (16)
README.mdROADMAP.mdSources/SwiftASB/Transport/CodexCLIExecutableResolver.swiftTests/SwiftASBTests/Public/CodexAppServerDiagnosticsTests.swiftTests/SwiftASBTests/Public/CodexAppServerLiveIntegrationTests.swiftTests/SwiftASBTests/Public/CodexAppServerTestSupport.swiftTests/SwiftASBTests/Public/CodexAppServerTests.swiftTests/SwiftASBTests/Transport/CodexCLIExecutableResolverTests.swiftTools/AgentSB/tests/test_cli.pyTools/AgentSB/tests/test_tools.pydocs/agents/reports/2026-06-11-agentsb-schema-review.mddocs/maintainers/interactive-lifecycle-release-boundary.mddocs/maintainers/quicktype-codegen-notes.mddocs/maintainers/v1-public-api-audit.mddocs/releases/v1.7.3.mdscripts/generate-wire-types.sh
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d0919e79d3
ℹ️ 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".
| index($0, "next meaningful work after the ") && index($0, "patch release") { | ||
| gsub("`v" old_version "`", "`v" new_version "`") | ||
| } | ||
| index($0, "patch prep") && index($0, "updates the current release reference again") { | ||
| gsub("`v" old_version "`", "`v" new_version "`") |
There was a problem hiding this comment.
In the standard release flow, release.sh invokes this hook before committing the bump, but this line-oriented whitelist misses ROADMAP's Current Patch Release Slice entries such as This slice records..., ### Planned for..., and the release-notes/tagging bullets; it also misses the wrapped patch prep sentence because the two substrings are on different lines. Running the hook on this tree for 1.7.4 leaves README at v1.7.4 while ROADMAP still contains v1.7.3 in that current-release section, which makes future release audit docs inconsistent.
Useful? React with 👍 / 👎.
1 participant
Release
schema/codex-cli-0-139-refreshmainupdates behind pull request review and CIv1.7.3will be created after CI and the review-comment gate pass, so failed or still-discussed release candidates do not get taggedReview Loop
Before merge and tagging,
scripts/repo-maintenance/release.shwatches CI and stops on review comments unless the maintainer has already addressed or resolved them and reruns with--review-comments-addressed.