Fix winget publish

[spoorcc]

Summary by CodeRabbit

Release Notes

• Chores
  • Updated GitHub Actions workflow configuration to enable required external connections.

[coderabbitai]

Warning

Review limit reached

@spoorcc, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 22 minutes and 17 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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: cdcf572d-9c93-4a73-9cb5-68d2c5e28dd1

📥 Commits

Reviewing files that changed from the base of the PR and between 598d9bc and 5a754c8.

📒 Files selected for processing (2)

• .github/workflows/winget-publish.yml
• .github/workflows/winget.yml

Walkthrough

The step-security/harden-runner egress allowlist in .github/workflows/winget-publish.yml is updated to include index.crates.io:443, permitting outbound HTTPS connections to the Rust crate index from the hardened runner.

Changes

WinGet Publish Workflow Egress Allowlist

Layer / File(s)	Summary
Add index.crates.io to harden-runner allowed-endpoints .github/workflows/winget-publish.yml	Appends index.crates.io:443 to the allowed-endpoints list so the hardened runner permits egress to the Rust crate index over HTTPS.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• dfetch-org/dfetch#1263: Introduced the step-security/harden-runner configuration in the same winget-publish.yml workflow that this PR extends with the index.crates.io:443 endpoint.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Fix winget publish' is vague and does not clearly describe the specific change made to the workflow file.	Make the title more specific, such as 'Allow outbound connections to index.crates.io in winget publish workflow' to better convey the actual change.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix-winget

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}