release: prepare v1.8.0#95
Conversation
|
Warning Review limit reached
Next review available in: 51 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughSwiftASB v1.8.0 adds ChangesSwiftASB v1.8.0: sleep kind, wire refresh, compatibility window
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)
✨ 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 |
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 `@Tests/SwiftASBTests/Protocol/CodexAppServerProtocolTests.swift`:
- Line 16: The protocol encoding tests in CodexAppServerProtocolTests are
accepting the new initializer fields but never asserting they stay out of the
serialized JSON. Update the affected fixture assertions around the Codable
payload checks to verify that mcpServerOpenaiFormElicitation and multiAgentMode
are absent from the encoded output, using the existing encoding/JSON inspection
helpers in these test cases so the wire contract is locked down.
🪄 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: db0dd994-05b8-4626-a19c-efc1ad4e765d
⛔ Files ignored due to path filters (1)
Sources/SwiftASB/Generated/CodexWire/Latest/CodexLifecycleV2Batch+JSONValue.swiftis excluded by!**/generated/**
📒 Files selected for processing (22)
README.mdROADMAP.mdSources/SwiftASB/Public/CodexAppServer+WireMapping.swiftSources/SwiftASB/Public/CodexThread+RecentTurns.swiftSources/SwiftASB/Public/CodexTurnHandle.swiftSources/SwiftASB/SwiftASB.docc/CodexWorkspace.mdSources/SwiftASB/Transport/CodexCLIExecutableResolver.swiftTests/SwiftASBTests/Protocol/CodexAppServerProtocolTests.swiftTests/SwiftASBTests/Public/CodexAppServerLiveApprovalProbeTests.swiftTests/SwiftASBTests/Public/CodexAppServerLiveElicitationProbeTests.swiftTests/SwiftASBTests/Public/CodexAppServerLiveIntegrationTests.swiftTests/SwiftASBTests/Public/CodexAppServerTests.swiftTests/SwiftASBTests/Public/CodexAppServerTurnLifecycleTests.swiftTests/SwiftASBTests/Transport/CodexCLIExecutableResolverTests.swiftTools/AgentSB/tests/test_cli.pyTools/AgentSB/tests/test_tools.pydocs/maintainers/interactive-lifecycle-release-boundary.mddocs/maintainers/quicktype-codegen-notes.mddocs/maintainers/v1-public-api-audit.mddocs/maintainers/v1-public-api-symbol-inventory.mddocs/releases/v1.8.0.mdscripts/generate-wire-types.sh
Release
schema/codex-cli-0-142-refreshmainupdates behind pull request review and CIv1.8.0will 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.