Update the pinned Miniconda installer used by Python environment tests. Find the pin, choose a version available for supported platforms, preserve coverage across conda major versions, and identify the relevant tests and download-cache effects.
Bump the pinned Miniconda version for the Python conda env tests.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The Python env tests download and install Miniconda. They pin an exact installer version. This skill tells you how to move a pin.
One file holds every conda pin:
community/python/python-test-env/common/src/com/intellij/python/test/env/common/PredefinedPyEnvironments.kt
| Entry | Role |
|---|---|
CONDA | The default. @PyEnvTestCaseWithConda and LocalCondaRule use it. Keep it on the newest build. |
CONDA_24 | An old pin. It covers the conda.core.index.get_index branch of the helper script. |
CONDA_25 | An old pin. It covers the conda.core.subdir_data.SubdirData branch. |
There is no second place. The provider builds the download URL from the pin, and it verifies no checksum:
community/python/python-test-env/conda/src/com/intellij/python/test/env/conda/CondaPyEnvironmentProvider.kt
To find every consumer of a pin, search the repository for PredefinedPyEnvironments.CONDA.
A pin is the installer version token, not a plain conda version. The shape is
py<python>_<conda>-<build>, for example py312_26.7.1-1.
The provider expands the token into one of these names:
Miniconda3-<token>-Windows-x86_64.exeMiniconda3-<token>-Linux-x86_64.shMiniconda3-<token>-Linux-aarch64.shMiniconda3-<token>-MacOSX-arm64.shhttps://repo.anaconda.com/miniconda/. The page lists every installer with its date and
its sha256.Miniconda3-latest-*. The cache key holds the token, so a
floating name breaks reproducibility.MacOSX-x86_64 builds after py313_25.7.0-2.py312 prefix unless you have a reason to change it. The prefix only sets the Python
of the base install. Each test environment gets its own Python from the spec.CondaPackagingToolHelperTest runs against CONDA_24, CONDA_25, and CONDA. It protects the
version branches in community/python/helpers/conda_packaging_tool.py.
CONDA for a normal bump.ENVIRONMENTS_TO_TAGS in the same file, and add the entry to the
@RunOnEnvironments list of that test.CONDA reaches the same major. Two entries on one major waste a
download.A move of CONDA can remove coverage without a test failure. CONDA supplies the newest major to
CondaPackagingToolHelperTest. A move from conda 26 to conda 27 therefore leaves conda 26
untested, and every test stays green. Before you move CONDA across a major, add a constant for
the major you leave behind, and add it to @RunOnEnvironments.
ShortenPathTest holds the literal Miniconda3-py312_24.9.2-0-MacOSX-arm64. It is sample text for
a path-shortening assertion, and no code reads the version. Leave it alone.
The tests cache in ~/.cache/intellij-python-test-env/:
downloads/ holds the installer.conda/Miniconda3-<token>-<os>-<arch>/ holds the install.The token is part of the directory name. A bump therefore downloads about 150 MB again, and it leaves the old directory on disk. Delete an old directory by hand when you need the space.
Conda 25 added a terms-of-service gate on the default Anaconda channels. The provider runs
conda tos accept for pkgs/main and pkgs/r before it creates an environment, and it ignores a
failure. An older conda has no tos subcommand. You need no new work here for a bump.
Every command below needs the network, and each conda environment downloads about 150 MB. Run the
commands from the monorepo root. In a community checkout, drop the community/ prefix, and skip
the intellij.python.junit5Tests commands. That module is ultimate only.
./community/tests.cmd --module intellij.python.test.env.junit5 --test com.intellij.python.test.env.junit5.conda.showcase.PyEnvWithCondaShowCaseTest
./tests.cmd --module intellij.python.junit5Tests --test com.intellij.python.junit5Tests.env.tests.conda.CondaSdkCreatorTest
./tests.cmd --module intellij.python.junit5Tests --test com.intellij.python.junit5Tests.env.tests.packaging.CondaPackagingToolHelperTest
community/python/python-sdk/backend/resources/sdks.json lists the Miniconda builds that the
product offers to a user. It needs a sha256 for every artifact, and
community/python/build/src/org/jetbrains/intellij/build/pycharm/sdks/CondaUpdater.kt generates
it. That file is separate from the env tests.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Implement or update IntelliJ `AnAction` classes and their `plugin.xml` registrations. Keep labels and descriptions in message bundles, configure optional icons, and launch suspending work through the event coroutine scope so synchronous action handling does not freeze the IDE.
Move IntelliJ JPS test modules to Bazel and diagnose failures that occur only under Bazel. The guide helps trace missing dependencies, plugins, test data, and runfiles, then verify the generated target and migrated tests.
Write or review Kotlin and Java code in line with IntelliJ project conventions. The guidance covers language choice, formatting, sealed types, threading annotations, and safe handling of control flow exceptions so changes fit the surrounding codebase.
Create, amend, or rename IntelliJ commits with messages that follow the project’s ticket and label formats. Keep each commit focused, explain the reason and decision in the body when needed, and pass the message safely through the shell or PowerShell.
Compare how Python type checkers interpret a code snippet or file. The script runs selected tools, including ty, pyrefly, basedpyright, mypy, and zuban, then produces a Markdown report with verdicts, timings, and each checker's diagnostic output.
Shape Compose Desktop UI code by keeping composables focused on rendering and placing application decisions in presenters or coordinators. Get guidance on state ownership, effects, reusable component APIs, lazy-list keys, animation, and performance for individual UI changes.