Bump 5.0.0

[GyuH13]

Update zenoh as default rmw

[gemini-code-assist]

Code Review

This pull request updates the Open Manipulator setup to version 5.0.0, switching the default RMW implementation to rmw_zenoh_cpp and adding update notification logic to the container script. Feedback on these changes suggests using a heredoc for .bashrc setup in the Dockerfile to improve readability. For the container script, recommendations include extracting duplicated update-checking logic into a function, using jq instead of sed for robust JSON parsing, defining the display box width as a constant, renaming variables for consistency, and referencing a tracking ticket for temporary notices.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[gemini-code-assist]

To improve readability and maintainability, consider using a cat with a heredoc to append these lines to .bashrc instead of chaining multiple echo commands.

RUN cat <<EOF >> ~/.bashrc
source /opt/ros/${ROS_DISTRO}/setup.bash
source ${COLCON_WS}/install/setup.bash
alias cb='colcon build --symlink-install --cmake-args -DCMAKE_BUILD_TYPE=Release'
alias omy_ai='ros2 launch open_manipulator_bringup omy_ai.launch.py'
alias omx_ai='ros2 launch open_manipulator_bringup omx_ai.launch.py'
alias zenohd='ros2 run rmw_zenoh_cpp rmw_zenohd'
export ROS_DOMAIN_ID=30
export RMW_IMPLEMENTATION=rmw_zenoh_cpp
EOF

[gemini-code-assist]

Instead of a generic (remove later) comment, it's good practice to create a technical debt ticket in your issue tracker and reference it here (e.g., # TODO(PROJ-123): Remove rmw_zenoh notice). This makes the temporary code easier to track and ensures it won't be forgotten.

[gemini-code-assist]

This logic is duplicated from the start_container function (lines 37-41). To improve maintainability, you should extract this into a new function and call it from both places.

Additionally, the variable GIT_VER should be renamed to LATEST_VER for consistency with start_container.

Suggested change

	CURRENT_VER=$(get_current_version)
	GIT_VER=$(get_latest_version)
	if update_available "${CURRENT_VER}" "${GIT_VER}"; then
	print_update_notice "${CURRENT_VER}" "${GIT_VER}"
	fi
	CURRENT_VER=$(get_current_version)
	LATEST_VER=$(get_latest_version)
	if update_available "${CURRENT_VER}" "${LATEST_VER}"; then
	print_update_notice "${CURRENT_VER}" "${LATEST_VER}"
	fi

[gemini-code-assist]

The width 52 is also used in print_rmw_zenoh_notice. To improve maintainability and ensure consistency, consider defining this value as a constant at the top of the script, for example: BOX_WIDTH=52.

[gemini-code-assist]

Parsing JSON with sed is fragile and can break if the API response format changes, even slightly (e.g., with extra whitespace). Using a dedicated JSON parser like jq would be much more robust and readable.

For example:

tag=$(echo "${json}" | jq -r '.tag_name')

You may want to add a check to ensure jq is installed on the host system, or add it to the developer environment setup instructions.

[gemini-code-assist]

For clarity and consistency, consider renaming the local variable git_ver to latest_ver. This makes the function's purpose more generic, as it compares a 'current' version with a 'latest' version, regardless of the source.

Suggested change

	local current="$1"
	local git_ver="$2"
	if [ -z "${git_ver}" ]; then
	return 1
	fi
	if [ "${git_ver}" = "${current}" ]; then
	return 1
	fi
	local newer
	newer=$(echo -e "${current}\n${git_ver}" | sort -V | tail -1)
	[ "${newer}" = "${git_ver}" ]
	local current="$1"
	local latest_ver="$2"
	if [ -z "${latest_ver}" ]; then
	return 1
	fi
	if [ "${latest_ver}" = "${current}" ]; then
	return 1
	fi
	local newer
	newer=$(echo -e "${current}\n${latest_ver}" | sort -V | tail -1)
	[ "${newer}" = "${latest_ver}" ]