Fix Windows invocation of rust-build-release

[leynos]

Summary

• invoke the Build release step via uv run --script so Windows runners resolve the script path correctly

Testing

• make lint

---

https://chatgpt.com/codex/tasks/task_e_68cf436db9748322a98de40dd68859dd

Summary by Sourcery

Fix Windows invocation of the rust-build-release GitHub Action by using uv run --script and adding shell safety options

Bug Fixes:

• Invoke release build script with uv run --script to resolve script path correctly on Windows runners

Enhancements:

• Add set -euo pipefail to the run step for stricter error handling

[coderabbitai]

Summary by CodeRabbit

• Chores
  • Improved release build workflow reliability by enforcing stricter error handling during the build step.
  • Standardised script execution in the release pipeline for more consistent outcomes across environments.
  • Enhanced failure transparency in CI, making issues surface earlier and more clearly.
  • No user-facing changes; this only affects the automation behind release builds.

Walkthrough

Replace direct script invocation in the composite GitHub Action with a multi-line shell block enabling strict shell options and executing the Python script via uv run --script using GITHUB_ACTION_PATH.

Changes

Cohort / File(s)	Summary
GitHub Action execution flow \.github/actions/rust-build-release/action.yml	Switch run step to a shell block with set -euo pipefail; invoke the Python script via uv run --script using $GITHUB_ACTION_PATH instead of direct path execution.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    actor Dev as Workflow
    participant GA as GitHub Action (rust-build-release)
    participant Sh as Shell (set -euo pipefail)
    participant UV as uv runner
    participant Py as Python script

    Dev->>GA: Invoke composite action
    GA->>Sh: Start shell block (strict mode)
    Sh->>UV: uv run --script $GITHUB_ACTION_PATH/...
    UV->>Py: Execute main Python script
    Py-->>UV: Exit code
    UV-->>Sh: Propagate status
    Sh-->>GA: Propagate status
    GA-->>Dev: Step result

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

A shell with stricter lines now plays,
uv steps in to run the maze.
No silent slips, no hidden fail,
The script sets sail on safer trail.
Pipelines neat, the logs will sing — ✅
Release we build, with steady wing.

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title Check	✅ Passed	Confirm that the title succinctly and accurately summarise the primary change: fixing the Windows invocation of the rust-build-release action by altering how the release script is executed. State that the title is concise, specific, and directly reflects the changes described in the PR description and file diff. Keep the title unchanged.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.
Description Check	✅ Passed	Indicate that the PR description directly matches the changeset: it states switching the GitHub Action run step to use "uv run --script" to fix Windows runners resolving the script path, notes testing via "make lint", and includes a reference link.

✨ Finishing touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch codex/fix-syntax-error-in-rust-build-release

---

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

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

The pull request updates the GitHub Action invocation for the rust-build-release step on Windows by switching from a direct script path call to a multiline shell block with strict error handling and using uv run --script for correct path resolution.

Flow diagram for new script invocation in rust-build-release action

flowchart TD
  A["Start Build Release Step"] --> B["Set shell options: -euo pipefail"]
  B --> C["Run: uv run --script $GITHUB_ACTION_PATH/src/main.py"]
  C --> D["Continue workflow"]

Loading

File-Level Changes

Change	Details	Files
Enhance Windows compatibility for the build-release step invocation	Replaced direct script invocation with a multiline run block Added set -euo pipefail to enforce strict shell error handling Switched to uv run --script "$GITHUB_ACTION_PATH/src/main.py" for correct script path resolution	.github/actions/rust-build-release/action.yml

Possibly linked issues

• Add upload-codescene-coverage action #1: PR fixes rust-build-release invocation on Windows, resolving script path issues that led to Docker command timeouts.

---

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 there - I've reviewed your changes and they look great!

---

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.}