Repository navigation
chore: release v0.1.0-alpha.3 - #27
Merged
Merged
Conversation
Records what landed after the previous release PR: the queued-turn rule and discovery-poll counters, typed filesystem requests and watches, the Windows Node/libuv process and console semantics, the half-close API and lingering close for HTTP/WebSocket servers, and caret dependency requirements. release-plz reports 'the repository is already up-to-date' because main's manifests (0.1.0-alpha.3) are ahead of the registry (0.1.0-alpha.2), so it proposes no further release PR; publishing requires merging a release-plz-* branch, which this is.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (12)
💤 Files with no reviewable changes (6)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughChangesAlpha.3 changelog updates
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~3 minutes Change: Other Merge Risk: ⚪ Minimal · up to No executable behavior changes or concrete merge-blocking risks are identified. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
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.
Records in each crate's 0.1.0-alpha.3 section what landed after the previous release PR (#19):
AsyncIo::poll_shutdown; caret dependency requirements (Use caret requirements for published dependencies instead of exact pins #25).HalfClose/shutdown()andlinger_close(Lingering close for HTTP and WebSocket servers; half-close API (#21) #23).linger_timeout,bind_with,with_optionsandstop_by(Lingering close for HTTP and WebSocket servers; half-close API (#21) #23, closing turnloop-http servers close with unread peer bytes (RST drops the final response on macOS/Windows) #21).closelingers instead of resetting the peer.Why this PR exists: release-plz logs "the repository is already up-to-date", because main's manifests (0.1.0-alpha.3) are ahead of the registry (0.1.0-alpha.2), so it proposes no further release PR. Publishing requires merging a
release-plz-*branch, and 0.1.0-alpha.3 is still unpublished: its first attempt failed on the semver baseline, and the second on Trusted Publishing rejecting theworkflow_runtrigger (both fixed in #18 and #24). Merging this publishes 0.1.0-alpha.3 from current main, after thecrates-ioenvironment approval.Summary by CodeRabbit
New Features
Bug Fixes
Documentation