Skip to content

Conversation

@marcoesters
Copy link
Contributor

@marcoesters marcoesters commented Jul 2, 2025

Description

CI runs, particularly on Windows, have been unstable, and often fail to install conda-standalone because of a 400 HTTP status code. It is possible that this is due to a problem in conda-anaconda-telemetry: anaconda/conda-anaconda-telemetry#127

Here is an example run: https://github.com/conda/constructor/actions/runs/16053138375/job/45589231931?pr=1011

A new version has been released and hotfixed (AnacondaRecipes/repodata-hotfixes#257), but Miniconda does not carry that version, yet.

Auto-update conda to install the new version. Using the latest conda allows including such hotfixes in the future and can be a good canary for issues with new conda versions.

Since dependencies are installed from conda-forge, use Miniforge instead of an updated telemetry plug-in.

Checklist - did you ...

  • Add a file to the news directory (using the template) for the next release's release notes?
  • Add / update necessary tests?
  • Add / update outdated documentation?

@github-project-automation github-project-automation bot moved this to 🆕 New in 🔎 Review Jul 2, 2025
@conda-bot conda-bot added the cla-signed [bot] added once the contributor has signed the CLA label Jul 2, 2025
@marcoesters marcoesters changed the title Use the latest conda for tests Use Miniforge for tests Jul 8, 2025
This reverts commit a929d69.
@marcoesters
Copy link
Contributor Author

Closing this since the new installers work.

@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🔎 Review Jul 21, 2025
@marcoesters marcoesters deleted the auto-update-conda branch November 11, 2025 00:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed [bot] added once the contributor has signed the CLA

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

2 participants