Skip to content

Pinning updates: name the changed pins and the packages that use them - #153

Merged
Tobias-Fischer merged 1 commit into
mainfrom
pinning-report-detail
Oct 24, 2026
Merged

Tobias-Fischer merged 1 commit into
mainfrom
pinning-report-detail

Conversation

@Tobias-Fischer

Copy link
Copy Markdown
Collaborator

The update-conda-forge-pinning report (e.g. #94) said which packages to rebuild, but not:

  • which pins had changed;
  • which packages use a changed pin directly, as opposed to depending on one that does;
  • whether any migration was new.

So it wasn't clear why only jazzy rebuilds in #94. The reason is shaderc 2026.3 → 2026.4, which only jazzy's gz_ogre_next_vendor uses; #152 drops that dependency.

Per distribution, the report now shows:

  • the changed pins, before → after;
    • those used by packages in a table, with the packages that use them directly;
    • the rest folded away;
  • how many packages use a changed pin and how many depend on one, with the direct users listed first;
  • the new migrations in bold, or "none new" when the pins change with conda-forge-pinning itself.

A pin whose value only changes its quoting (gfal2 '6' → 6) no longer counts as changed.

Preview from #94's pins (dependency check stubbed out):

humble and jazzy as the new report shows them

Migrations: elfutils0196, go_macos, gsl28, gstreamer128, hdf52, libboost190, libhwloc2150, proj99, urdfdom6; none new (the pins below change with conda-forge-pinning itself); finished (now part of the base pinning): giflib6

humble

Changed pins no package uses (8)
  • libopenvino: 2026.4.0 → 2026.4.1
  • libopenvino-dev: 2026.4.0 → 2026.4.1
  • libtrintrin: (none) → 0.3
  • ocaml-compiler: (none) → ocaml
  • ocaml-compiler-version: (none) → 5.4.0
  • shaderc: 2026.3 → 2026.4
  • zig-compiler: (none) → zig
  • zig-compiler-version: (none) → 0.17.0

No package uses a changed pin: nothing to rebuild.

Dependency check (linux-64): ✅ no new conflicts

jazzy

changed pin before → after used directly by
shaderc 2026.3 → 2026.4 gz_ogre_next_vendor
Changed pins no package uses (7)
  • libopenvino: 2026.4.0 → 2026.4.1
  • libopenvino-dev: 2026.4.0 → 2026.4.1
  • libtrintrin: (none) → 0.3
  • ocaml-compiler: (none) → ocaml
  • ocaml-compiler-version: (none) → 5.4.0
  • zig-compiler: (none) → zig
  • zig-compiler-version: (none) → 0.17.0

Rebuild 51 of 1203 packages: 1 uses a changed pin, 50 depend on one. 51 packages get build_number: 28 in distros/jazzy/pkg_additional_info.yaml

Packages to rebuild (51)
  • gz_ogre_next_vendor: uses shaderc
  • desktop_full: depends on ros_gz_sim_demos
  • easynav_playground_kobuki: depends on easynav_playground_kobuki_worlds
  • easynav_playground_kobuki_worlds: depends on gz_sim_vendor
  • easynav_playground_omni: depends on easynav_playground_omni_worlds
  • easynav_playground_omni_worlds: depends on gz_sim_vendor
  • easynav_playground_summit: depends on easynav_playground_summit_worlds
  • easynav_playground_summit_worlds: depends on gz_sim_vendor
  • easynav_playground_tiago: depends on easynav_playground_tiago_worlds
  • easynav_playground_tiago_worlds: depends on gz_sim_vendor
  • gz_gui_vendor: depends on gz_rendering_vendor
  • gz_rendering_vendor: depends on gz_ogre_next_vendor
  • gz_ros2_control: depends on gz_sim_vendor
  • gz_ros2_control_demos: depends on gz_sim_vendor
  • gz_sensors_vendor: depends on gz_rendering_vendor
  • gz_sim_vendor: depends on gz_rendering_vendor
  • iiwa14_moveit_config: depends on lbr_description
  • iiwa7_moveit_config: depends on lbr_description
  • irobot_create_gz_bringup: depends on gz_ros2_control
  • irobot_create_gz_plugins: depends on gz_gui_vendor
  • irobot_create_gz_sim: depends on irobot_create_gz_plugins
  • kinova_gen3_7dof_robotiq_2f_85_moveit_config: depends on kortex_description
  • kortex_description: depends on gz_ros2_control
  • lbr_bringup: depends on gz_ros2_control
  • lbr_demos_advanced_cpp: depends on lbr_description
  • lbr_demos_advanced_py: depends on lbr_description
  • lbr_demos_cpp: depends on lbr_bringup
  • lbr_demos_py: depends on lbr_bringup
  • lbr_description: depends on gz_ros2_control
  • lbr_fri_ros2: depends on lbr_description
  • lbr_fri_ros2_stack: depends on lbr_bringup
  • lbr_ros2_control: depends on lbr_description
  • med14_moveit_config: depends on lbr_description
  • med7_moveit_config: depends on lbr_description
  • moveit2_tutorials: depends on kinova_gen3_7dof_robotiq_2f_85_moveit_config
  • nav2_bringup: depends on ros_gz_sim
  • nav2_minimal_tb3_sim: depends on ros_gz_sim
  • nav2_minimal_tb4_sim: depends on ros_gz_sim
  • ros_gz: depends on ros_gz_sim
  • ros_gz_sim: depends on gz_sim_vendor
  • ros_gz_sim_demos: depends on gz_sim_vendor
  • simulation: depends on ros_gz_sim
  • turtlebot3: depends on turtlebot3_navigation2
  • turtlebot3_gazebo: depends on gz_sim_vendor
  • turtlebot3_navigation2: depends on nav2_bringup
  • turtlebot3_simulations: depends on turtlebot3_gazebo
  • turtlebot4_gz_bringup: depends on irobot_create_gz_plugins
  • turtlebot4_gz_gui_plugins: depends on gz_gui_vendor
  • turtlebot4_navigation: depends on nav2_bringup
  • turtlebot4_simulator: depends on turtlebot4_gz_gui_plugins
  • ur_simulation_gz: depends on gz_ros2_control

Dependency check (linux-64): ✅ no new conflicts

Tests: a new test_pin_report_lists_the_direct_users; all 58 tool tests pass.

When merging: this changes tools/, so the merge regenerates every distribution's build branches and cancels any runs in progress. Best merged after humble's rebuild finishes.

🤖 Generated with Claude Code

The update-conda-forge-pinning report said which packages to rebuild, but not
which pins had changed, which packages use them directly (as opposed to
depending on one that does), or whether any migration was new. So it wasn't
clear from #94 why only jazzy rebuilds: shaderc 2026.3 -> 2026.4, which only
jazzy's gz_ogre_next_vendor uses.

Per distribution the report now shows the changed pins (before -> after),
those that packages use in a table with their direct users, the rest folded
away; the rebuild list says how many use a changed pin and how many depend on
one, direct users first; the migrations line names the new ones or says there
are none. A pin whose value only changes its quoting ('6' -> 6) isn't a change.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Tobias-Fischer Tobias-Fischer added the build:none PR build: build no packages, only run the checks (tooling, CI or docs changes) label Oct 24, 2026
@Tobias-Fischer
Tobias-Fischer enabled auto-merge (squash) October 24, 2026 04:44
@Tobias-Fischer
Tobias-Fischer merged commit 651231e into main Oct 24, 2026
8 checks passed
@Tobias-Fischer
Tobias-Fischer deleted the pinning-report-detail branch October 24, 2026 04:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build:none PR build: build no packages, only run the checks (tooling, CI or docs changes)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant