Skip to content

Is the "channels" warning an issue? #132

Closed

Description

@jGaboardi

issue:

"channels" set on the "environment-file" do not match "channels" set on the action!

I am getting the above warning, which seems to be thrown regardless of OS/Python version, (Ubunutu/3.7, for example). The workflow runs without failing so it doesn't appear to be a problem, but I am wondering if I doing something incorrectly or something could be more streamlined. Unless I am mistaken (which could absolutely be the case), the name of the only channel I am using (conda-forge) is exactly the same in the workflow file and the environment file.

associated files:

Activity

  1. goanpeca commented on Dec 30, 2020

    @goanpeca
    Member

    Hi @jGaboardi, thanks for the report.

    That is indeed unexpected. We will check!

  2. self-assigned this
    on Dec 30, 2020
  3. jGaboardi commented on Dec 30, 2020

    @jGaboardi
    Author

    Hi @jGaboardi, thanks for the report.

    That is indeed unexpected. We will check!

    Super, thanks!

  4. bollwyvl commented on Dec 30, 2020

    @bollwyvl
    Contributor
  5. bnavigator commented on Jan 7, 2021

    @bnavigator

    Any news on this? I see the same.

    workflow:

    - name: Setup Conda
            uses: conda-incubator/setup-miniconda@v2
            if: matrix.distribution == 'conda'
            with:
              channels: conda-forge
              auto-update-conda: true
              python-version: ${{ matrix.python }}
              activate-environment: test-env
              environment-file: ./Slycot/.github/conda-env/test-env.yml
              auto-activate-base: false

    test-env.yml

    channels:
      - conda-forge
  6. goanpeca commented on Mar 19, 2026

    @goanpeca
    Member

    Closing. Cchannel configuration handling has been significantly reworked. Commit 7fc0a85 fixed double channel configuration adding. The new conda-remove-defaults input also provides explicit control. If you still see spurious warnings with the latest version, please open a new issue.

  7. added this to the v4.0.0 milestone on May 31, 2026
  8. added theissue type on Jun 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

reso:completedThis issue has been resolved or fixedtype:bugSomething isn't working

Type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions