Fix Rust PyPI trusted publishing permission

[vinitkumar]

Summary

• add id-token: write to the Rust wheel release workflow permissions

Why

The rust-v0.3.0 release built all wheels successfully, but the PyPI publish job failed during trusted publishing because the workflow did not grant OIDC token permissions.

Validation

• lat check: passed

Summary by Sourcery

Build:

• Update Rust wheel build workflow permissions to include id-token: write for PyPI trusted publishing.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Grant OIDC id-token write permission in the Rust wheel build workflow so PyPI trusted publishing can succeed.

File-Level Changes

Change	Details	Files
Grant OIDC id-token write permission required by PyPI trusted publishing in the Rust wheel release workflow.	Extend workflow-level permissions to include id-token: write alongside contents: read so jobs can request OIDC tokens for PyPI publish. Rely on GitHub’s fine-grained permissions model instead of using broader default permissions for the workflow.	.github/workflows/build-rust-wheels.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path=".github/workflows/build-rust-wheels.yml" line_range="22" />
<code_context>

 permissions:
   contents: read
+  id-token: write

 jobs:
</code_context>
<issue_to_address>
**🚨 suggestion (security):** Consider scoping `id-token: write` to the specific job that requires it rather than at the workflow level.

This makes OIDC tokens available to every job. To follow least-privilege, only enable `id-token: write` in the `permissions` block of the specific jobs that actually need it, keeping the workflow-wide permissions minimal.

Suggested implementation:

```
permissions:
  contents: read

jobs:
  # Build wheels for Linux

```

To fully implement least-privilege, add a `permissions` block to the specific job(s) that actually require OIDC, for example:
```yaml
jobs:
  some-job-that-needs-oidc:
    permissions:
      id-token: write
      contents: read
    steps:
      ...
```
Adjust the job name and permissions according to the actual job in this workflow that uses OIDC (e.g. for cloud auth/deploy). Other jobs should omit `id-token: write`.
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

🚨 suggestion (security): Consider scoping id-token: write to the specific job that requires it rather than at the workflow level.

This makes OIDC tokens available to every job. To follow least-privilege, only enable id-token: write in the permissions block of the specific jobs that actually need it, keeping the workflow-wide permissions minimal.

Suggested implementation:

permissions:
  contents: read

jobs:
  # Build wheels for Linux

To fully implement least-privilege, add a permissions block to the specific job(s) that actually require OIDC, for example:

jobs:
  some-job-that-needs-oidc:
    permissions:
      id-token: write
      contents: read
    steps:
      ...

Adjust the job name and permissions according to the actual job in this workflow that uses OIDC (e.g. for cloud auth/deploy). Other jobs should omit id-token: write.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (44ebfc7) to head (3d31d97).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #315   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            6         6           
  Lines          569       569           
=========================================
  Hits           569       569           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.