release: prepare v11.0.0#121
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
📝 WalkthroughWalkthroughThis PR is a straightforward version bump from release-candidate ChangesSpeakSwiftly 11.0.0 Release Version Update
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 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.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 04ed7d9055
ℹ️ 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".
| .package(url: "https://github.com/swiftlang/swift-docc-plugin", from: "1.1.0"), | ||
| .package(url: "https://github.com/apple/swift-nio.git", from: "2.83.0"), | ||
| .package(url: "https://github.com/gaelic-ghost/SpeakSwiftly.git", from: "11.0.0-alpha.7"), | ||
| .package(url: "https://github.com/gaelic-ghost/SpeakSwiftly.git", from: "11.0.0"), |
There was a problem hiding this comment.
Keep the API dependency baseline in sync
After this bump, the package now resolves SpeakSwiftly from 11.0.0, but API.md still states that the current package depends on SpeakSwiftly from 11.0.0-alpha.7 in its Supported Versions section. Because this is the operator-facing compatibility contract, releasing this commit would publish contradictory dependency guidance; update that API baseline alongside the manifest change.
Useful? React with 👍 / 👎.
Release
release/v11.0.0mainupdates behind pull request review and CIv11.0.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.Summary by CodeRabbit
Chores
Documentation