You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Upload regression in 1.15.0 blocks conda-forge publication #943
In #892, --channel was repurposed from a deprecated alias for --label and made incompatible with --user.
Conda-forge hit this after updating to 1.16.0 on November 3. In this cmdstanpy build, the package built and passed its tests, but uploads to cf-staging failed until the retry loop timed out. Because conda-forge-ci-setup uses this command, other feedstocks using the affected client can fail the same way.
-c without -u needs a separate compatibility follow-up. In 1.16.0, upload -c dev treats dev as a destination and enters the resolver, which may require a choice of service, channel, or namespace. A name matching both an anaconda.org owner and a writable repo target prompts in a terminal and exits with an error without one. The linked build fails before reaching this code. The follow-up should cover noninteractive CI uploads and preservation of the intended owner and label.
Please prioritize a patch release and clarify how future deprecations will preserve existing upload automation. Keep this issue open until a fixed package is published and affected uploads are confirmed working.
changed the title [-]Regression: --user and --channel uploads fail since 1.15.0 and block conda-forge publication[/-][+]Upload regression in 1.15.0 blocks conda-forge publication[/+]on Nov 3, 2026
Activity
[-]Regression: --user and --channel uploads fail since 1.15.0 and block conda-forge publication[/-][+]Upload regression in 1.15.0 blocks conda-forge publication[/+]prjemian commentedon Nov 4, 2026
Seeing the same upload failure in apstools-feedstock.
The package build, tests, artifact inspection, and output validation all pass. The push workflow fails only while uploading to cf-staging:
https://github.com/conda-forge/apstools-feedstock/actions/runs/41723890806/job/126340036409
The failure repeats across reruns, including attempt 4, and consistently reports:
The relevant package is apstools 1.7.13, build 0. It has not appeared on the public conda-forge channel because the staging upload never completes.
Rerendering locally with conda-smithy 2026.10.24 and conda-forge-pinning 2026.11.02.15.51.50 produces no changes.