micro-ROS / micro-ROS/micro_ros_platformio
Allow freezing the micro-ROS package versions
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 334
- Forks
- 111
- PR merge metrics
- No merged PRs in 30d
Description
I got back to working on my project after a couple of months. When I tried to build it, it no longer compiled because the library builder pulled newer version of micro-ROS packages that contained API changes that were not compatible with my code.
I think this library should either be tied to specific versions of the packages and have a library auto-update workflow (similar to the on micro_ros_arduino) or allow the user to specify the versions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the library builder and the code that resolves micro-ROS package versions. Determine whether the project should pin versions, provide user-selected versions, or support an update workflow; the issue does not decide between these options. Done requires builds to avoid unexpected incompatible package updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, embedded-iot
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100