Daily conda-forge pinning PRs that rebuild only what changed pins affect

[Tobias-Fischer]

Daily conda-forge pinning PRs, one per distribution, that rebuild only what the changed pins affect instead of everything.

rs <distro> update-pinning / @robostack-bot update-conda-forge-pinning [<distro>... | all]

1. Moves the distribution's conda-forge pinning to the latest version, with the migrations that are done for its dependencies:
   • the pin comes from conda_forge_pinning_version / conda_forge_migrations in distro.yaml;
   • or from shared/pinning/conda_forge.yaml for distributions that follow it.
2. Re-renders conda_build_config.yaml.
3. Plans the rebuild with vinca-rebuild-plan (Add vinca-rebuild-plan: rebuild only what a pinning change affects vinca#168). It rebuilds packages with a changed pin among their build/host requirements, plus everything that depends on them (host or run, transitively).
   • Partial rebuild: those packages get a per-package build number above everything on the channel. When the mutex run_constraints change, the mutex gets a new build at the same version, so every other published package stays installable.
   • Full rebuild (build number + mutex minor bump, as before) only when more than half of the packages are affected.
4. Checks the dependencies (check_dependency_compat.py, linux-64) before and after. The PR is labelled dependency-conflict only when the new pins add conflicts; conflicts that already exist are listed in a collapsed section.

The PR body lists, each in a collapsed section:

• the packages to rebuild and why;
• the migrations used (or finished, now part of the base pinning);
• the migrations waiting for named conda-forge feedstocks;
• the migrations that don't concern the distribution.

The bot runs it daily for every distribution, so each distribution has one PR, refreshed in place.

Example (lyrical, run locally): 2026.09.25 → 2026.10.08, new migrations gsl28 and libhwloc2150, vtk970 finished. It rebuilds 2 of 1117 packages (visp uses gsl, spatio_temporal_voxel_layer uses openexr), and the dependency check reports no new conflicts.

check_dependency_compat.py

• Takes the requirements of every selected package from vinca; --source recipes keeps the old behaviour. recipes/ only holds unbuilt packages with skip-existing, so the old default checked an incomplete set.
• Network calls are retried.
• --stale now handles ros2-* names and -devel pins (e.g. libboost_devel vs. the libboost run dependency).
• A run-only dependency that just needs a newer glibc than the build floor is a note, not a conflict. For example, conda-forge's libcamera needs glibc 2.34.

Also

• vinca is pinned to robostack-integration b5c524b, which adds the rebuild planner.
• The PR-cache evictions of One shared package selection for all distributions (vinca extends, ros2-* names, no kilted) #8 are reset.

🤖 Generated with Claude Code