[Tobias-Fischer]

Recipes, snapshots and build workflows now come from vinca-rs, a Rust rewrite of vinca. It reuses pixi-build-ros for package.xml parsing and rattler-build's crates for rendering.

Changes

• vinca-rs is a pixi source dependency (pixi-build-rust), pinned by commit.
• rs <d> generate-recipes runs vinca-rs generate. Already-published recipes are matched by exact name, version and build string, which rattler-build's own renderer computes, so -n is gone from testpr.yaml.
• rs <d> gha runs vinca-rs workflow from .github/build-template.yaml. That template carries what robostack.py used to patch into vinca-gha's output: run name, concurrency, per-distro token secret, contents: read, env. The job steps live in .github/actions/build-recipes, so a job is a few lines and many more jobs fit GitHub's 500 KiB limit.
  • Each job needs only the jobs building its dependencies, not the whole previous stage. A failure then only skips what depends on it.
  • vinca-rs workflow --json writes vinca-gha --json: write the batched stages instead of a workflow vinca#201's stage format, with the same ids, so Staged builds for pull requests and releases #216 can switch to it. --stage-barriers plans for its slots.
• rs <d> create-snapshot runs vinca-rs snapshot. The output is identical to vinca-snapshot (jazzy at jazzy/2026-10-05: 2469 packages), in 23 s instead of 6 min.
• check-deps, pinning and rebuild planning read requirements from vinca-rs requirements. Python vinca stays for pinning render/update, the rebuild planner and the sort tools.
• Additional recipes: vinca-rs requires an override: reason when an additional recipe replaces a released package (Raise an error if snapshot and additional_recipes are conflicting vinca#126).
  • The autoware packages that lyrical and rolling took from humble "until released" are released now, so they are dropped and come from the releases again.
  • Rolling's autoware_lanelet2_extension patches are refreshed for 1.1.0.
  • The remaining overrides got reasons: rplidar_ros, rtabmap, mujoco_vendor, and lyrical's newer autoware_lanelet2_extension.

What changes in the packages
vinca-rs was compared with vinca 74d1e85 (RoboStack/vinca#200) by meaning, for every distro and platform. It produces the same recipes (20/20: humble 2531/2467/2181/2181/1837, …), with the same sources, patches, build numbers, metadata and test files. The intended differences:

• Install check: every ament package gets a package_contents test for its package.xml (Automatically add existence tests vinca#108).
• Conda-forge wrappers: packages that only wrap a conda-forge package (generate_dummy_package_with_run_deps) depend on just it and the mutex. Their variant hash changes, so about 20 per distro and platform are rebuilt once.
• One build script per recipe: platform selectors are resolved at generation, so each recipe carries only its platform's build script.
• Build types:
  • The CMake script lost its catkin/ROS 1 parts: build_catkin becomes build_cmake.
  • A package without <build_type> that builds with ament_cmake* is ament (async_web_server_cpp, mrt_cmake_modules).
• Python variants: conditional_python_dependency (Conditionally build Python-dependent Lyrical libraries across Pythons 3.12-3.14 #193) is supported, with conditions evaluated (condition part of the dependency tag is ignored in some case vinca#189). For lyrical it produces the same recipes as vinca.

Tested

• Build-branch-style runs of the new workflow from this branch, for humble with uploads off:
  • linux-64: 22/22 built and tested.
  • win-64: 19/19 built and tested.
• Locally on osx-arm64, generate-recipes → rs humble build built and tested the 20 recipes that skip-existing left.
• pixi run rs check passes, and pytest tools/tests gives 81 passed.

Notes

• vinca-rs depends on pixi-build-ros's library target, prefix-dev/pixi#7526. Until that lands it is pinned to that PR's branch.
• Not in this PR: Set build number on vinca.yaml instead of pkg_additional_info.yaml vinca#173 (build-number offsets).

🤖 Generated with Claude Code

[Tobias-Fischer]

Stacked three commits on this PR, so its CI is the end-to-end test of the shared rosdep mappings:

• c93fb85: eight rosdep keys that only pixi-build-ros's copy of the mappings had (crypto++, iproute2, lua-dev, python3-dbus, python3-pygnssutils-pip, python3-tabulate, python3-types-pyyaml, rtklib). pixi's cartographer entry is left out: it's a ROS package, and its mapping was removed on purpose (ros-humble 09bcd470).

• Rebuilds of the packages that gained dependencies from them:

  • plotjuggler gains lua in humble, jazzy, lyrical and rolling;
  • launch and nav2_common gain types-pyyaml in lyrical and rolling;
  • orbbec_camera gains tabulate in rolling.

  The build numbers come from robostack-bot rebuild. With the commits undone, generate-recipes drops exactly these packages and their ros-<distro>-* aliases, and nothing else changes. Built locally on osx-arm64: plotjuggler (humble), launch (rolling) and nav2_common (lyrical) all pass.

• robostack-bot sync-pixi-mappings: a daily PR on prefix-dev/pixi that copies shared/robostack.yaml and distros/*/robostack.yaml to pixi-build-ros (feat(pixi-build-ros): RoboStack's rosdep mappings per distribution, one lookup shared with RoboStack prefix-dev/pixi#7533). It's off until vars.PIXI_FORK and secrets.PIXI_SYNC_TOKEN are set. distros/noetic/robostack.yaml holds noetic's Qt 5 mappings for pixi; it has no vinca.yaml, so it isn't built.

The lookup itself moves into pixi-build-ros (prefix-dev/pixi#7533); vinca-rs uses it in Tobias-Fischer/vinca-rs#3, which generates byte-identical recipes.

— Claude (AI assistant), on behalf of @Tobias-Fischer

[Tobias-Fischer]

Superseded by a stack of four PRs, one per commit, so each part can be reviewed (and merged) on its own: #221 (vinca-rs) → #222 (package fixes) → #223 (rosdep mappings shared with pixi-build-ros) → #224 (per-package files and dependency fixes). Together they hold exactly this PR's changes, without the temporary test commits.

— Claude