esteve/Release ROS Robot

Automate ROS package releases with bloom-release, using a release-please/release-plz-style workflow

Trust Signals

name	description	required	default
mode	Action mode: prepare (create release PR) or release (run bloom-release)	no	release
oauth-token	PAT for release mode. Falls back to the BLOOM_OAUTH_TOKEN environment variable. Not used in prepare mode (which uses GITHUB_TOKEN).	no	—
github-user	GitHub username that owns the rosdistro fork used by bloom-release. Falls back to the BLOOM_GITHUB_USER environment variable. Only used in release mode.	no	—
repository	Repository name as registered in rosdistro (e.g., my_ros_package). Required in release mode.	no	—
release-repository	Release repository URL (e.g., https://github.com/ros2-gbp/my_package-release.git). Required in release mode.	no	—
rosdistro	ROS distribution to release (e.g., rolling, jazzy, humble). Required in release mode.	no	—
track	Bloom track to use (e.g., rolling, jazzy). Required in release mode.	no	—
dry-run	Run in dry-run mode without actually releasing	no	false
exclude-paths	Newline-separated list of POSIX glob patterns to exclude from package.xml discovery. Useful when the repository contains test fixtures or vendored code with package.xml files that are not real ROS packages.	no	""
version-bump	Version bump type: auto (detect from conventional commits), patch, minor, or major	no	auto
base-branch	Base branch for release PR (only used in prepare mode)	no	main

name	description
pr-created	Whether a release PR was created (prepare mode only)
released	Whether a release was performed (release mode only)
version	The version that was released or will be released
rosdistro	The ROS distribution that was released to (release mode only)
pr-url	The URL of the release PR (prepare mode) or rosdistro pull request (release mode)