8000 Upload regression in 1.15.0 blocks conda-forge publication · Issue #943 · anaconda/anaconda-client · GitHub
[go: up one dir, main page]

Skip to content

Upload regression in 1.15.0 blocks conda-forge publication #943

Open

Description

@jezdez

Since 1.15.0, anaconda upload rejects the command used by conda-forge-ci-setup:

anaconda upload package.conda --user=cf-staging --channel=main

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.

The proposed fix in #942 restores the alias when --user is explicit. conda-forge/anaconda-client-feedstock#68 backports it to 1.16.0 build 1.

-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.

Activity

  1. 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
  2. prjemian commented on Nov 4, 2026

    @prjemian

    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:

    -c/--channel no longer equals labels, did you mean --label?
    -c/--channel cannot be used with -u/--user.
    

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      0