Update maturin version to latest stable release

[coderabbitai]

The MATURIN_VERSION environment variable in .github/workflows/build-wheels.yml is currently set to "1.6.0", which is outdated. The latest stable release is 1.11.5 (released 9 January 2026).

Upgrading to the newer version would provide access to bug fixes and new features developed over the past seven months.

Related PR: #25
Comment: #25 (comment)

Requested by: @leynos

[traycerai]

Plan

Observations

The maturin version 1.6.0 is referenced in three locations: the GitHub Actions workflow environment variable (file:.github/workflows/build-wheels.yml), the build-wheels action default parameter (file:.github/actions/build-wheels/action.yml), and the development dependencies (file:pyproject.toml). The workflow uses maturin for building native Python wheels across multiple platforms (Linux x86_64/aarch64, macOS x86_64/arm64, Windows x86_64) via both the messense/maturin-action and a custom composite action. Upgrading from 1.6.0 to 1.11.5 provides seven months of improvements including free-threaded Python support, Python 3.13t compatibility, iOS/Android support, PEP 639 compliance, and various bug fixes.

Approach

The implementation will update all three occurrences of the maturin version to 1.11.5 to maintain consistency across the build pipeline. This ensures that both CI workflows and local development environments use the same version. The update is straightforward since maturin maintains backward compatibility and the workflow already uses explicit version pinning. No changes to build commands or configuration are required, as the existing maturin invocations remain compatible with the newer version.

Implementation Steps

1. Update GitHub Actions Workflow Environment Variable

File: file:.github/workflows/build-wheels.yml

Locate line 11 where the MATURIN_VERSION environment variable is defined and update the version string from "1.6.0" to "1.11.5":

env:
  MATURIN_VERSION: "1.11.5"

This environment variable is referenced in:

• Line 66: manylinux x86_64 build step using messense/maturin-action
• Line 84: manylinux aarch64 build step using messense/maturin-action
• Line 100: macOS/Windows build step passing to the custom build-wheels action

2. Update Build Wheels Action Default Parameter

File: file:.github/actions/build-wheels/action.yml

Locate line 20 where the maturin-version input parameter default value is defined and update it from "1.6.0" to "1.11.5":

inputs:
  maturin-version:
    description: Maturin version to install
    required: false
    default: "1.11.5"

This default value is used on line 37 when installing maturin via pip in the composite action's shell step.

3. Update Development Dependencies

File: file:pyproject.toml

Locate line 27 in the [dependency-groups] section under dev and update the maturin version constraint from "==1.6.0" to "==1.11.5":

[dependency-groups]
dev = [
    "pytest",
    "pytest-bdd",
    "ruff",
    "pyright",
    "pytest-timeout",
    "pytest-xdist",
    "syrupy",
    "ty",
    "maturin==1.11.5",
]

This ensures developers using uv sync --group dev for local development will install the same maturin version as CI.

4. Verification Steps

After making the changes, verify the update by:

1. Check workflow syntax: Ensure the YAML files remain valid after the version string update
2. Review action references: Confirm that the messense/maturin-action at commit 47fbb7acd3db01f7830330b50689bd15135c12b9 (lines 64 and 82 in build-wheels.yml) is compatible with maturin 1.11.5
3. Test local build: Run uv sync --group dev to verify the updated pyproject.toml dependency resolves correctly
4. Monitor CI execution: After merging, observe the build-wheels workflow to ensure all platform builds (Linux x86_64/aarch64, macOS x86_64/arm64, Windows x86_64) complete successfully with the new version

Notes

• The messense/maturin-action GitHub Action accepts any maturin version via the maturin-version parameter, so no action version update is required
• The existing build commands and arguments remain compatible with maturin 1.11.5
• The manylinux 2_28 compatibility setting (lines 32, 37, 68, 86) continues to work with the newer version
• No changes to file:rust/cuprum-rust/Cargo.toml or maturin configuration in file:pyproject.toml (lines 147-151) are necessary

Import In IDE

🤖 Prompt for AI Agents

## Observations

The maturin version 1.6.0 is referenced in three locations: the GitHub Actions workflow environment variable (`file:.github/workflows/build-wheels.yml`), the build-wheels action default parameter (`file:.github/actions/build-wheels/action.yml`), and the development dependencies (`file:pyproject.toml`). The workflow uses maturin for building native Python wheels across multiple platforms (Linux x86_64/aarch64, macOS x86_64/arm64, Windows x86_64) via both the messense/maturin-action and a custom composite action. Upgrading from 1.6.0 to 1.11.5 provides seven months of improvements including free-threaded Python support, Python 3.13t compatibility, iOS/Android support, PEP 639 compliance, and various bug fixes.

## Approach

The implementation will update all three occurrences of the maturin version to 1.11.5 to maintain consistency across the build pipeline. This ensures that both CI workflows and local development environments use the same version. The update is straightforward since maturin maintains backward compatibility and the workflow already uses explicit version pinning. No changes to build commands or configuration are required, as the existing maturin invocations remain compatible with the newer version.

## Implementation Steps

### 1. Update GitHub Actions Workflow Environment Variable

**File:** `file:.github/workflows/build-wheels.yml`

Locate line 11 where the `MATURIN_VERSION` environment variable is defined and update the version string from "1.6.0" to "1.11.5":

```yaml
env:
  MATURIN_VERSION: "1.11.5"
```

This environment variable is referenced in:
- Line 66: manylinux x86_64 build step using `messense/maturin-action`
- Line 84: manylinux aarch64 build step using `messense/maturin-action`
- Line 100: macOS/Windows build step passing to the custom build-wheels action

### 2. Update Build Wheels Action Default Parameter

**File:** `file:.github/actions/build-wheels/action.yml`

Locate line 20 where the `maturin-version` input parameter default value is defined and update it from "1.6.0" to "1.11.5":

```yaml
inputs:
  maturin-version:
    description: Maturin version to install
    required: false
    default: "1.11.5"
```

This default value is used on line 37 when installing maturin via pip in the composite action's shell step.

### 3. Update Development Dependencies

**File:** `file:pyproject.toml`

Locate line 27 in the `[dependency-groups]` section under `dev` and update the maturin version constraint from "==1.6.0" to "==1.11.5":

```toml
[dependency-groups]
dev = [
    "pytest",
    "pytest-bdd",
    "ruff",
    "pyright",
    "pytest-timeout",
    "pytest-xdist",
    "syrupy",
    "ty",
    "maturin==1.11.5",
]
```

This ensures developers using `uv sync --group dev` for local development will install the same maturin version as CI.

### 4. Verification Steps

After making the changes, verify the update by:

1. **Check workflow syntax**: Ensure the YAML files remain valid after the version string update
2. **Review action references**: Confirm that the `messense/maturin-action` at commit `47fbb7acd3db01f7830330b50689bd15135c12b9` (lines 64 and 82 in build-wheels.yml) is compatible with maturin 1.11.5
3. **Test local build**: Run `uv sync --group dev` to verify the updated pyproject.toml dependency resolves correctly
4. **Monitor CI execution**: After merging, observe the build-wheels workflow to ensure all platform builds (Linux x86_64/aarch64, macOS x86_64/arm64, Windows x86_64) complete successfully with the new version

### Notes

- The `messense/maturin-action` GitHub Action accepts any maturin version via the `maturin-version` parameter, so no action version update is required
- The existing build commands and arguments remain compatible with maturin 1.11.5
- The manylinux 2_28 compatibility setting (lines 32, 37, 68, 86) continues to work with the newer version
- No changes to `file:rust/cuprum-rust/Cargo.toml` or maturin configuration in `file:pyproject.toml` (lines 147-151) are necessary

---

Execution Information

Branch: main
Commit: d8606d6

---

💡 Tips

Supported Commands (Inside Comments)

• Use @traycerai generate to iterate on the previous version of the implementation plan.

Supported Commands (Inside Description)

• Add @traycerai ignore anywhere in the ticket description to prevent this ticket from being processed.
• Add @traycerai branch:<branch-name> anywhere in the ticket description to specify the target branch for the implementation plan.

Community

• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.