Set macOS-26 GitHub Actions runner in conda-forge feedstock
Session from conda-forge-agent-traces on Hugging Face by xhochy · BSD-3-Clause · condensed by Coders Talk
Click a segment to jump to that moment
8msession
0interventions
GOAL
Switch a conda-forge feedstock's CI to use the macos-26 GitHub Actions runner via conda-forge.yml/recipe config, then re-render with conda-smithy.
- +0Prompt · +0Use macos-26 as the GitHub Actions runner; use conda-forge skill and search web on how to do this via conda-forge.yml or recipe/conda_build_config.yaml, then conda-smithy rerender.
- +0mAgent did · +0mInspected the feedstock's conda-forge.yml, recipe files, and conda-forge skill docs to understand current config.
- +0mAgent did · +0mSearched conda-forge docs and conda-smithy source (configure_feedstock.py) to find how github_actions_labels / runs_on is set, and inspected .ci_support and workflow files.
- +5mAgent did · +5mEdited recipe/conda_build_config.yaml to add github_actions_labels with osx/arm64 selector set to macos-26.
- +7mAgent did · +7mRan conda-smithy rerender to regenerate CI configs from the updated recipe.
- +7mAgent did · +7mVerified changes by inspecting conda_build_config.yaml, .ci_support/osx_arm64_.yaml, the workflow file, git diff, and ran conda-smithy lint, confirming clean output.
- +8mOutcome · +8mFeedstock updated: runs_on changed from macos-15 to macos-26 across recipe/conda_build_config.yaml, .ci_support/osx_arm64_.yaml, and .github/workflows/conda-build.yml; conda-smithy lint passed clean.
VERDICT
I'd tell the agent upfront to check conda-smithy's GITHUB_ACTIONS_RUNS_ON mapping directly instead of spending several web searches first, since the source code fetch is what actually gave the answer. No corrections were needed here—the agent researched, edited the config, re-rendered, and the lint passed clean on the first try.