Skip to content

fix(ci): skip already-published dependency packages in conda uploads - #381

Merged
Xuwznln merged 1 commit into
devfrom
fix/conda-upload-skip-existing-deps
Nov 19, 2026
Merged

Xuwznln merged 1 commit into
devfrom
fix/conda-upload-skip-existing-deps

Conversation

@Xuwznln

@Xuwznln Xuwznln commented Nov 19, 2026

Copy link
Copy Markdown
Collaborator

Why

The manual ROS 2 / full upload for v0.13.0a1 (run 44541199446) failed on all four platforms at "Upload packages after successful tests":

[ERROR] ('file linux-64/ros-humble-unilabos-msgs-0.12.2-h81b34b9_1.conda already exists for package ros-humble-unilabos-msgs version 0.12.2', 409)
RuntimeError: 上传失败:ros-humble-unilabos-msgs-0.12.2-h81b34b9_1.conda

An extensions-only build rebuilds the message packages (recipes() puts msgs before ros2 and full). The message version did not change since 0.12.3, so the rebuilt files already exist on the channel. build_conda_release.py upload passes --skip-existing only for noarch packages and mcp, so the platform message packages fail with 409. Upload stops there, and unilabos-full (a platform package that sorts after them) never gets uploaded. The noarch unilabos-ros2 0.13.0a1 packages did go up on linux-64 before the failure.

Change

  • FRAMEWORK_PLATFORM_PACKAGES = {"unilabos", "unilabos-full"}: these must be new on every release. If the same file already exists, upload fails as before.
  • Every other package, such as the ROS message packages and mcp, is a reused dependency and uploads with --skip-existing. noarch packages keep --skip-existing because every matrix job builds them.
  • --force is still never passed.

Tests

  • New test_extension_upload_skips_published_message_packages reproduces the failing case: an extensions-only linux-64 upload with both message packages, unilabos-ros2 and unilabos-full. It fails on the current dev script and passes with this change.
  • tests/app/test_no_ros_installation.py: 38 passed.
  • Ruff findings on the two files are unchanged from dev. None are new.

After merge

Re-dispatch unilabos-conda-build.yml (extensions only, jazzy + humble + full, upload on) with source_ref set to the merge commit. unilabos-full and unilabos-ros2 are metapackages without a source: section, and their recipes are unchanged, so the packages built are the same as from the tag.

An extensions-only release rebuilds the ROS message packages next to
unilabos-ros2 and unilabos-full. When the message version is unchanged,
the rebuilt files already exist on the uni-lab channel, so the first
upload returns 409 and the job stops before unilabos-full is uploaded.
The 0.13.0a1 ROS 2 / full upload stopped exactly there on all four
platforms.

Only the framework platform packages (unilabos, unilabos-full) must be
new on every release. Every other package is a reused dependency and now
uploads with --skip-existing, as noarch packages and mcp already did.
Nothing is overwritten: --force is never passed.
@Xuwznln
Xuwznln merged commit 92ba3ae into dev Nov 19, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant