Publish this repo to the ESP Component Registry

I'm planning to publish this repository to the ESP Component Registry. My idea is to create several registry components based on ROS distributions, such as micro-ros-humble and micro-ros-jazzy. I'll start with rolling and see how it works out. Any suggestions or ideas are welcome.

@Amronos

What are your thoughts? @Amronos @EugenioCollado

That sounds good to me! Feel free to ping if you need any help.

There is currently no micro-ros namespace on the ESP Component Registry, so someone needs to apply for it. Should I submit the application, or would it be more appropriate for a maintainer of the micro-ROS organization to do so? If the latter, who should I contact?

A reasonable ownership structure might be to have a micro-ROS organization maintainer serve as the namespace owner, with me added as a namespace member.

FYI: https://docs.espressif.com/projects/idf-component-manager/en/latest/publish/explanation_registry_roles.html

I will handle the micro-ros namespace on the ESP Component Registry. I will let you know as soon as it has been granted

The namespace request has been approved, it is called micro-ros. I have tried to add both of you to the namespace but when searching by your github username No users found. If you have any idea on how to add you to the namespace tell me.

Another option that maybe is a good idea is to create a Github Action Workflow to automate the upload of new releases every time a new commit has been pushed on any of the branches of the components: https://github.com/espressif/upload-components-ci-action

@Narukara

I have been able to assign the developer role on the created components to @Narukara

I also just created an account on the components registry. Could you add me also? Thanks!

I have been able to assign the developer role on the created components to @Narukara

The micro-ros namespace has already been created. But it doesn't show up on my Permissions page, and I don't have visibility into any components under the namespace. 🤔

On the other hand, if we want to use OIDC authentication, it looks like someone with the appropriate permissions will first need to create the component and perform some initial configuration.

I also just created an account on the components registry. Could you add me also? Thanks!

I have granted you developer permissions too

I don't have much knowledge about the ESP Component Registry, so I don't why it does not show you your new role

@EugenioCollado

Is micro-ros/rolling a suitable component name? If micro-ROS wants to publish other components in the future, this naming could become a bit confusing.

I think we should try using OIDC authentication. @EugenioCollado Could you help configure it? I assume the setup would look something like this:

I have granted uploader permissions in the kilted component for an eventual upload-esp-registry.yml workflow:

👌 I'll try publishing kilted first.

I noticed that having a component directory name that differs from the name published to the registry can cause issues, as described here: espressif/esp-idf#14532. If we adopt a one-component-per-distribution approach, it would make it difficult to build the examples conveniently when working in this repository.

I am therefore considering switching back to a single-component approach. The main challenge with this approach is version management. One possible solution would be to use the ROS 2 distribution's release year as the major version in the ESP Component Registry semantic version:

22.x.y → Humble
23.x.y → Iron
24.x.y → Jazzy
25.x.y → Kilted
26.x.y → Lyrical

I have already opened a PR with the necessary changes for Kilted. #378

Another question is how to handle Rolling. One option would be not to publish Rolling to the registry at all and instead have users depend on it through a Git dependency like this:

dependencies:
  micro_ros_espidf_component:
    git: https://github.com/micro-ROS/micro_ros_espidf_component.git
    version: rolling

Another possibility would be to version Rolling as a prerelease of the next distribution, for example 27.0.0-rolling.20260805. Note that registry dependencies do not consider prerelease versions by default. Users must explicitly request a prerelease version.

I like your suggested approach. I have approved the PR

All existing distributions (Humble, Jazzy, Kilted, and Rolling) have now been published to the ESP Component Registry, so I'm closing this issue. Thank you all for your help!

Navigation Menu

Repository navigation

Publish this repo to the ESP Component Registry #369

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Publish this repo to the ESP Component Registry #369

Description

Activity

Narukara commented on Jul 14, 2026

Amronos commented on Jul 14, 2026

Narukara commented on Jul 27, 2026

EugenioCollado commented on Jul 27, 2026

EugenioCollado commented on Jul 28, 2026

EugenioCollado commented on Jul 28, 2026

Amronos commented on Jul 28, 2026

Narukara commented on Jul 28, 2026

EugenioCollado commented on Jul 28, 2026

Narukara commented on Jul 29, 2026

EugenioCollado commented on Jul 30, 2026

Narukara commented on Aug 5, 2026

Narukara commented on Aug 5, 2026

Narukara commented on Aug 5, 2026

EugenioCollado commented on Aug 10, 2026

Narukara commented on Aug 24, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions