Prepare 0.14.2 and fix WinGet egress policy#1298
Conversation
Add static.crates.io:443 and objects.githubusercontent.com:443 to the winget-publish egress allowlist. cargo-binstall fetches the komac source tarball from static.crates.io to read binstall metadata (even for binary installs), and the komac binary/dfetch MSI are served from objects.githubusercontent.com. These two missing endpoints caused the WinGet publish step to fail for 0.14.0 (index.crates.io) and 0.14.1 (static.crates.io) respectively. Bump version to 0.14.2 and open the changelog for the new cycle.
|
Warning Review limit reached
More reviews will be available in 49 minutes and 26 seconds. 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 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 credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. 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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (37)
WalkthroughThe WinGet publish workflow's runner hardening step is updated to allow outbound connections to ChangesWinGet publish egress fix and version bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested labels
Suggested reviewers
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 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 |
Propagate the version bump to all BDD feature expected outputs. Note: this is the manual equivalent of running script/release.py — pending discussion on whether to revert the version bump and keep __version__ at 0.14.1 until actual release time.
The version bump and feature file propagation belong at release time (via script/release.py), not in the post-release prep commit. Only the CHANGELOG unreleased header and the winget egress fix are needed on this branch.
Add static.crates.io:443 and objects.githubusercontent.com:443 to the
winget-publish egress allowlist. cargo-binstall fetches the komac source
tarball from static.crates.io to read binstall metadata (even for binary
installs), and the komac binary/dfetch MSI are served from
objects.githubusercontent.com. These two missing endpoints caused the
WinGet publish step to fail for 0.14.0 (index.crates.io) and 0.14.1
(static.crates.io) respectively.
Bump version to 0.14.2 and open the changelog for the new cycle.
Summary by CodeRabbit