Rollout of GHA-based build workflows

[jaimergp]

This issue aggregates the different items involved in rolling out Github Actions as the default provider for builds.

• Disable special casing in conda-smithy and make GHA a default provider
  • feat: enable GHA for all of conda-forge conda-smithy#2478
  • Change native provider for arm platforms and all emulated providers t… conda-smithy#2485
  • ENH: update package version to 3.56.1 conda-smithy-feedstock#375
  • feat: add announcement for GHA #2768
• The default had to be rolled back to Azure in fix: back to azure conda-smithy#2488, released in 3.56.2 due to:
  • Figure out how to roll out GHA workflows upon rerenders from forks (#general > conda-smithy rerender for 3.56.1 resulting in broken builds)
    • Re-enable Github Actions as default provider for Linux and Windows conda-smithy#2495
    • Use Azure for Windows conda-smithy#2498
    • Allow mixing Github-hosted and self-hosted runners in github_actions_labels conda-smithy#2499
    • https://github.com/conda-forge/conda-smithy/releases/tag/v3.57.0
    • conda-smithy 3.57.0 conda-smithy-feedstock#378
• End admin migration (chore: end EnableGHAWorkflows migration admin-migrations#178)
• Fix mixing self-hosted and Github-hosted runners for GHA
  • conda-smithy 3.58.0 conda-smithy-feedstock#379
  • conda-smithy 3.58.1 conda-smithy-feedstock#380
• macOS concurrency is very limited: macOS GHA runners take very long to pick the job up conda-smithy#2486
  • Re-enable macOS on GHA
• Feature parity on Windows with Azure workflows: Unified interface for common conda-forge.yml tasks that should be independent of CI provider conda-smithy#2349
  • Re-enable Windows on GHA

[kratsg]

I have a slight issue where 3.56.2 doesn't seem to rollback to azure: conda-forge/fastframes-feedstock#1 . @chrisburr is aware but commenting for visibility.

Attempted steps to resolve this (due to the fact that the GHA smithy made its way into main for my feedstock)

• bot command (filed issue) @conda-forge-admin, please rerender @conda-forge-admin, please rerender fastframes-feedstock#9
• checked out that PR gh pr checkout 10
• revert the commit that did the switch to github actions git revert e763f29
• re-rendered with the latest 3.56.2 smithy: conda-smithy rerender (and committed)
• pushed back to the same PR

Seems to get me back to a sense of normalcy, and I'll merge this in, rebase my other fork, and that should get me back on track.

[jaimergp]

Some more behaviours I've observed:

• In ENH: update package version to 0.15.0 nono-feedstock#7 and [bot-automerge] storybook v10.2.17 storybook-feedstock#88, no workflows ran whatsoever. These are opened by our bot infra.
• pylangacq v0.21.0 pylangacq-feedstock#1 same, but it got merged (maybe by accident), and the workflow did run successfully on main.

At this point we assume that workflows added from PRs opened from forks of users not maintaining that repo won't run. So I asked @mgorny to open a couple of rerender-only PRs (using pixi exec --with "conda-smithy==3.56.1[channel=conda-forge/label/broken]" -c conda-forge -c conda-forge/label/broken conda-smithy rerender --no-check-uptodate to use the conda-smithy version that defaulted to GHA) to repos where he has not contributed:

• [DNM] Rerender for debugging purposes dav1d-feedstock#32
• [DNM] Test workflows storybook-feedstock#89

In dav1d, the workflows ran just fine. @mgorny maintains other feedstocks, so he's not a first time contributor. To check this, he asked another person who is not part of conda-forge to do the same: conda-forge/dav1d-feedstock#33. In this case, the GHA workflows require approval (good, that's expected, but also means that the GHA config did kick in!), and perhaps interestingly the Azure ones still run from main.

Since our bots are not first-time contributors, I don't think we should worry too much about this observation and it should be ok.

The interesting bit is storybook: in that case nothing happened, reproducing the behavior observed by @synapticarbors. Neither Azure nor GHA, no approval popup either. So I'm inclined to think this "bug" is repo-dependent. Maybe there's a configuration somewhere we are missing? Or it has to do with the creation dates?

dav1d was created on 2022-07-21. storybook on 2024-12-15. nono on 2026-03-03, pylanga a few days later. Did anything change in GHA policies between 2022 and 2024?

[jaimergp]

Good news, planting a disabled workflow in main to "enable" GHA for the first time seems to work. The workflow doesn't have to do anything. Just in case, it uses the same filename.

• ENH: update package version to 10.2.17 storybook-feedstock#91 shows how the disabled workflow shows up in feedstocks that have not rerendered yet (commit 784b3ad). Once it rerendered for Azure, the GHA workflow was deleted and it doesn't show up again (commit 815d660)
• [DNM] Test workflows storybook-feedstock#89 is what happened before planting the dummy workflow. After planting it, we get [DNM] Testing workflows storybook-feedstock#92, with the desired behavior

[jaimergp]

Ok, some more updates:

• Our current hypothesis is that repos created somewhere after Nov 2024 won't run GHA workflows unless has (or has had) a workflow under .github/workflows in main.
• As a result, we will run an admin-migrations migrator to populate the workflows with a dummy one to enable GHA for the existing repos. See Add migrator to enable GHA workflows admin-migrations#174.
• conda-smithy will also add a dummy conda-build.yml workflow after every rerender when GHA is not selected as a provider to make sure new repos are also pre-enabled. Add dummy GHA workflow to make sure Github Actions is enabled conda-smithy#2494

This should allow us to flip the default again to use GHA for Linux and Windows. macOS concurrency limits are still under investigation, so that platform will still use Azure for the time being.

Thanks @beckermr, @chrisburr and @mgorny for the discussions and debugging!

[beckermr]

Looks like the admin migrations job is working: conda-forge/relay-feedstock@d5e6583

It will be a few days likely before it finishes.

[beckermr]

Well I take that back. It is already at 1.6k feedstocks. Should be done by tomorrow morning.

[jaimergp]

With conda-smithy 3.57 out, users will start seeing Github Actions for Linux in their rerenders. Windows and macOS are still on Azure for the time being.