maturin-action

March 31, 2026 ยท View on GitHub

GitHub Actions

GitHub Action to install and run a custom maturin command with built-in support for cross compilation.

Usage

- uses: PyO3/maturin-action@v1
  with:
    command: build
    args: --release

To generate a GitHub Actions workflow for your project, try the maturin generate-ci github command.

mkdir -p .github/workflows
maturin generate-ci github > .github/workflows/CI.yml

Examples

If you want to build and publish a Python extension module for common Python versions, operating systems, and CPU architectures, take a look at the following examples:

Inputs

NameRequiredDescriptionTypeDefault
commandNomaturin command to runstringbuild
argsNoArguments to pass to maturin subcommandstring
maturin-versionNoThe version of maturin to use. Must match a tagged releasestringlatest
manylinuxNoControl the manylinux platform tag on linux, ignored on other platforms, use auto to build for lowest compatiblestringDefaults to auto for the publish command
targetNoThe --target option for Cargostring
containerNomanylinux docker container image namestringDefault depends on target and manylinux options, Set to off to disable manylinux docker build and build on the host instead.
docker-optionsNoAdditional Docker run options, for passing environment variables and etc.string
rust-toolchainNoRust toolchain name.stringDefaults to stable for Docker build. To use the latest available version for the host build, the user must specify this in the CI config or repo config.
rustup-componentsNoRustup componentsstringDefaults to empty
working-directoryNoThe working directory to run the command instringDefaults to the root of the repository
sccacheNoEnable sccache for faster buildsbooleanDefaults to false
before-script-linuxNoScript to run before the maturin command on Linuxstring

manylinux Docker container

By default, this action uses the following containers for supported architectures and manylinux versions.

ArchitectureManylinux versionDefault containerNote
x86_642010/2_12quay.io/pypa/manylinux2010_x86_64:latest
x86_642014/2_17quay.io/pypa/manylinux2014_x86_64:latest
x86_642_24quay.io/pypa/manylinux_2_24_x86_64:latestDeprecated
x86_642_28quay.io/pypa/manylinux_2_28_x86_64:latest
i6862010/2_12quay.io/pypa/manylinux2010_i686:latest
i6862014/2_17quay.io/pypa/manylinux2014_i686:latest
i6862_24quay.io/pypa/manylinux_2_24_i686:latestDeprecated
i6862_28quay.io/pypa/manylinux_2_28_i686:latest
aarch642014/2_17ghcr.io/rust-cross/manylinux2014-cross:aarch64
aarch642_24messense/manylinux_2_24-cross:aarch64Deprecated
aarch642_28ghcr.io/rust-cross/manylinux_2_28-cross:aarch64
armv7l2014/2_17ghcr.io/rust-cross/manylinux2014-cross:armv7
armv7l2_24messense/manylinux_2_24-cross:armv7Deprecated
armv7l2_28ghcr.io/rust-cross/manylinux_2_28-cross:armv7
ppc64le2014/2_17ghcr.io/rust-cross/manylinux2014-cross:ppc64le
ppc64le2_24messense/manylinux_2_24-cross:ppc64leDeprecated
ppc64le2_28ghcr.io/rust-cross/manylinux_2_28-cross:ppc64le
ppc642014/2_17ghcr.io/rust-cross/manylinux2014-cross:ppc64
s390x2014/2_17ghcr.io/rust-cross/manylinux2014-cross:s390x
s390x2_24messense/manylinux_2_24-cross:s390xDeprecated
s390x2_28ghcr.io/rust-cross/manylinux_2_28-cross:s390x
riscv642_31ghcr.io/rust-cross/manylinux_2_31-cross:riscv64
riscv642_39quay.io/pypa/manylinux_2_39_riscv64:latest
loongarch642_36ghcr.io/rust-cross/manylinux_2_36-cross:loongarch64

You can override it by supplying the container input. Note that if use official manylinux docker images for platforms other than x86_64 and i686, you will need to setup QEMU before using this action, for example

- name: Setup QEMU
  uses: docker/setup-qemu-action@v1
- uses: PyO3/maturin-action@v1
  with:
    command: build
    args: --release

Note that the actions/setup-python action won't affect manylinux build since it's containerized, so if you want to build for certain Python version for Linux, use -i pythonX.Y in the args option in PyO3/maturin-action instead, for example

- uses: PyO3/maturin-action@v1
  with:
    args: --release -i python3.10

Hardening Release pipelines

We recommend the following steps for hardening release pipelines:

  • When targeting PyPI, set --compatibility pypi to activate its pre-upload check
  • Set an explicit manylinux: version for each target to prevent silent regressions
  • Pin both maturin-action and maturin version, and use a service such as renovate to update them
strategy:
  matrix:
    platform:
      - target: aarch64-unknown-linux-gnu
        arch: aarch64
        manylinux: 2_28
      - target: armv7-unknown-linux-gnueabihf
        arch: armv7
        manylinux: 2_17

steps:
  # [...]
  - name: "Build wheels"
    uses: PyO3/maturin-action@86b9d133d34bc1b40018696f782949dac11bd380 # v1.49.4
    with:
      maturin-version: v1.11.5
      target: ${{ matrix.platform.target }}
      manylinux: ${{ matrix.platform.manylinux }}
      args: --release --locked --compatibility pypi

An example renovate configuration

// Maturin version used in maturin-action
{
  customType: "regex",
  managerFilePatterns: ["/.github/workflows/.*\\.yml$/"],
  matchStrings: ["maturin-version: (?<currentValue>v\\d+\\.\\d+\\.\\d+)"],
  depNameTemplate: "maturin",
  packageNameTemplate: "PyO3/maturin",
  datasourceTemplate: "github-releases",
},

Contributing

To build after code changes:

npm run all

License

This work is released under the MIT license. A copy of the license is provided in the LICENSE file.