greenroom-robotics/ROS Semantic Release Action
Uses semantic release to build and release ros packages as debians
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jun 30, 2026
- License
- None
Pinned Snippet
uses: greenroom-robotics/ros_semantic_release_action@431f9aa62af06e2d48ff1690e9083d8439ad3c24 # v2tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| token | The Github token with access to the packages repo and release api | yes | — |
| changelog | Should we generate and commit back a changelog? | — | true |
| github_release | Should we create a github release? | — | true |
| skip_tag | Should we skip creating a git tag? | — | false |
| skip_build | Should we skip building the packages? | — | false |
| public | Should the packages be public? | — | false |
| package | The package to release. If not set, all packages in the 'package_dir' will be released. | — | "" |
| package_dir | The directory to release packages from. If not set, the root of the repo will be used. | — | ./ |
| arch | The architecture to build for (eg amd64 or arm64). | — | amd64 |
| gpu | This will be passed into the Dockerfile as $GPU to enable GPU support. | — | false |
| ros_distro | The version of ros2 to build for (eg galactic or humble). This will be passed into the Dockerfile as $ROS_DISTRO. | — | iron |
| release_branches | The branches to release from. Comma separated list. | — | main,master,alpha |
| cli_branch | The branch of platform_cli to use | — | main |
| secrets | JSON string of secrets to pass to docker build (e.g. '{"API_TOKEN_GITHUB": "./.secrets/github_token", "apt_conf": "./.secrets/apt.conf"}') | — | {} |
| bot_slug | GitHub App slug to attribute the release commit to. Defaults to the greenroom App bot; set empty to fall back to semantic-release's default identity. | — | greenroom-gremlin |
Outputs
no outputs