pybind / pybind/scikit_build_example

Migrate conda CI from conda-build to rattler-build

Open
#209 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
148
Forks
39
Avg merge
8d 2h
Merged PRs (30d)
1

Description

🤖 AI text below 🤖

The Conda workflow uses conda-build with a conda.recipe/meta.yaml. This is showing its age: conda-build is now a conda plugin, and recent setup-miniconda default changes keep breaking the build (see #208 for the latest patch).

We should move to rattler-build, the maintained conda package builder from the prefix.dev / conda-forge folks. It is faster, does not need a full miniconda + conda-build install, and has an official GitHub Action.

Rough scope:

  • Add a recipe/recipe.yaml in the rattler-build schema (replacing conda.recipe/meta.yaml).
  • Replace the setup-miniconda + conda build steps in .github/workflows/conda.yml with prefix-dev/rattler-build-action (or a pixi-based build).
  • Keep the Python matrix and the pytest tests check.
  • Once green, drop the old conda.recipe/ and the conda-build-specific steps.

This is a template repo, so the recipe doubles as an example for downstream users — worth keeping it clean and current.

References:

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read .github/workflows/conda.yml and conda.recipe/meta.yaml first, then consult the rattler-build recipe schema and prefix-dev/rattler-build-action documentation. Done means recipe/recipe.yaml builds successfully across the existing Python matrix, pytest tests still runs, and the old conda.recipe/ and conda-build-specific workflow steps are removed.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, python
Domain
build-system, ci-cd
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
65/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.