Repository navigation
ci(conda): upload the macos-26-intel legs with the anaconda CLI (#2044) - #2049
Merged
Merged
Conversation
anaconda/actions/upload-package v0.3.1 installs its CLI from anaconda.sh/releases/stable/v0.2.1/ana-darwin-x86_64, which returns 404, so "Upload conda packages to Anaconda" fails on every Intel leg. In cron-conda.yml's conda-dist and create-release.yml's conda, that step now skips macos-26-intel, and "Upload conda packages to Anaconda (Intel)" runs there instead: it installs conda-forge's anaconda-client into base and makes the action's own `anaconda --token ... upload --user ...` call, with the same channel, labels and files, plus `--skip-existing`. Every other leg keeps the action. create-release.yml's per-leg check still gates both. releasing.rst states the Intel exception. test_release_gates.py's PUBLISHING_MARKERS recognises the CLI call as a route to anaconda.org. tests/project/test_conda_intel_cli_upload_2044.py evaluates both steps' `if:` per leg and runs the CLI step with a stand-in conda and anaconda; test_release_tags_the_run_sha_1634.py's pins of the action step's `if:` follow.
Owner
Author
|
GOOD TO GO at
UNVERIFIED: a real |
4 of 5 tasks
Contributor
|
Coverage: 91.54% (unit tier, Python 3.15,
Per-file detail: the |
Owner
Author
|
Ordering check on |
6 tasks done
This was referenced Oct 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
make pylint,make mypy,make isort)make testpasses, and a test case covers the changeWhat is the purpose of your pull request?
ci— changes to CI configuration files and scriptsDescription of your pull request and other information
Closes #2044. This is fix 3; fixes 1 and 2 landed in #2045. Per the owner's ruling, option (a): only the
macos-26-intellegs stop usinganaconda/actions/upload-package, whoseana-darwin-x86_64download returns 404.cron-conda.ymlandcreate-release.yml, the existing Upload conda packages to Anaconda step now skipsmacos-26-intel. A new Upload conda packages to Anaconda (Intel) step runs only there. It installsanaconda-clientfrom conda-forge and runsanaconda upload --user jarryshaw --skip-existingwith the same labels and package list. The token arrives throughenv:, the release step keeps thecheck_leggate, and an empty package list fails with::error.--skip-existingkeeps a file that already exists, where the action'sforce: truereplaces it.releasing.rstsays all of this.PUBLISHING_MARKERSintest_release_gates.pynow recognises the CLI call. Probed with a CLI-only job that had noenvironment:: the old markers missed it, and the new ones fail.tests/project/test_conda_intel_cli_upload_2044.pyfails onmain's workflows (18 failed) and passes here. This file plus the release gate and tag tests:219 passed.PR CI never runs Conda Update or Create Release, so the Intel step is unproven until a real run.