Repository navigation
Update conda-forge pinning - #94
robostack-bot-dev[bot] wants to merge 1 commit into
Conversation
ABI check (linux-64)humble linux-64: 1 to review (changed headers), 127 can be bumped on their own
127 packages can be bumped on their own (compatible: 71, no libraries: 56)
Compared with the newest builds on https://repo.prefix.dev/tobias-fischer/robostack-distro-test/linux-64 and https://conda.anaconda.org/robostack-staging/linux-64. jazzy linux-64: 4 to review (changed headers), 174 can be bumped on their own
174 packages can be bumped on their own (compatible: 93, no libraries: 81)
Compared with the newest builds on https://repo.prefix.dev/tobias-fischer/robostack-distro-test/linux-64 and https://conda.anaconda.org/robostack-jazzy/linux-64. rolling linux-64: **1 need their dependents rebuilt**, 2 to review (changed headers), 133 can be bumped on their own
133 packages can be bumped on their own (compatible: 89, no libraries: 44)
Compared with the newest builds on https://repo.prefix.dev/tobias-fischer/robostack-distro-test/linux-64 and https://repo.prefix.dev/robostack-rolling/linux-64. About this checkEach package this pull request built, compared with its newest released build (
Exported symbols are compared (the released packages are stripped, so struct layouts aren't); unchanged installed headers rule out layout and inline changes, changed ones are listed for review. Dependents to rebuild are the released ones linking to a changed library. A changed pin is part of the comparison. |
70fe9b4 to
0a74f4b
Compare
|
Just leaving this open as the bot would reopen it; but merge sync PRs instead |
ae0c7d0 to
91cd7ce
Compare
57e262b to
d3dc295
Compare
The package only wraps conda-forge's ogre-next (no OGRE-Next build of its own), but kept shaderc from the upstream package.xml. So every shaderc pin change rebuilt it and its 50 dependents (the Gazebo stack, nav2_bringup, the turtlebots, desktop_full, ...), as in the pinning update #94. New build 28 of just this package; its dependents don't need one. Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
…#153) 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>
d3dc295 to
5e9e317
Compare
Moves humble, jazzy, lyrical, rolling from conda-forge-pinning
2026.10.09.13.11.31to2026.10.25.00.13.22(shared/pinning/conda_forge.yaml).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):giflib6humble
Changed pins no package uses (10)
aws-crt-cpp:0.42.3→0.43.8dawn:(none)→20261023.194543libopenvino:2026.4.0→2026.4.1libopenvino-dev:2026.4.0→2026.4.1libtrintrin:(none)→0.3ocaml-compiler:(none)→ocamlocaml-compiler-version:(none)→5.4.0shaderc:2026.3→2026.4zig-compiler:(none)→zigzig-compiler-version:(none)→0.17.0No package uses a changed pin: nothing to rebuild.
Dependency check (linux-64): ✅ no new conflicts
Conflicts that already exist with the current pins (2)
gazebo,libfrankajazzy
Changed pins no package uses (10)
aws-crt-cpp:0.42.3→0.43.8dawn:(none)→20261023.194543libopenvino:2026.4.0→2026.4.1libopenvino-dev:2026.4.0→2026.4.1libtrintrin:(none)→0.3ocaml-compiler:(none)→ocamlocaml-compiler-version:(none)→5.4.0shaderc:2026.3→2026.4zig-compiler:(none)→zigzig-compiler-version:(none)→0.17.0No package uses a changed pin: nothing to rebuild.
Dependency check (linux-64): ✅ no new conflicts
lyrical
Changed pins no package uses (10)
aws-crt-cpp:0.42.3→0.43.8dawn:(none)→20261023.194543libopenvino:2026.4.0→2026.4.1libopenvino-dev:2026.4.0→2026.4.1libtrintrin:(none)→0.3ocaml-compiler:(none)→ocamlocaml-compiler-version:(none)→5.4.0shaderc:2026.3→2026.4zig-compiler:(none)→zigzig-compiler-version:(none)→0.17.0No package uses a changed pin: nothing to rebuild.
Dependency check (linux-64): ✅ no new conflicts
rolling
Changed pins no package uses (10)
aws-crt-cpp:0.42.3→0.43.8dawn:(none)→20261023.194543libopenvino:2026.4.0→2026.4.1libopenvino-dev:2026.4.0→2026.4.1libtrintrin:(none)→0.3ocaml-compiler:(none)→ocamlocaml-compiler-version:(none)→5.4.0shaderc:2026.3→2026.4zig-compiler:(none)→zigzig-compiler-version:(none)→0.17.0No package uses a changed pin: nothing to rebuild.
Dependency check (linux-64): ✅ no new conflicts
Migrations used (9)
elfutils0196: kept (already applied)go_macos: kept (already applied)gsl28: kept (already applied)gstreamer128: kept (already applied)hdf52: kept (already applied)libboost190: kept (already applied)libhwloc2150: kept (already applied)proj99: kept (already applied)urdfdom6: kept (already applied)Migrations waiting for our dependencies' feedstocks (3)
libffi37: waiting for rubypython314t: waiting for autobahn, bullet, coverage, cython, libodepython315: waiting for apriltag, autobahn, bullet, coverage, dartsimMigrations that don't concern humble, jazzy, lyrical, rolling (9)
azure_core_cpp1164: not relevant to generated recipeslibiio1: not relevant to generated recipeslibyarp3123: not relevant to generated recipesmpich5: not relevant to generated recipesocaml551: not relevant to generated recipespytorch213: not relevant to generated recipespytorch214: not relevant to generated recipesroot_base64004: not relevant to generated recipess2n177: not relevant to generated recipes🤖 robostack-bot