Skip to content

Bump 0.8.2#89

Merged
robotpilot merged 4 commits intojazzyfrom
main
Mar 18, 2026
Merged

Bump 0.8.2#89
robotpilot merged 4 commits intojazzyfrom
main

Conversation

@GyuH13
Copy link
Copy Markdown
Member

@GyuH13 GyuH13 commented Mar 18, 2026

BUMP 0.8.2
remove ai_server in s6-contents

@GyuH13 GyuH13 added the bump Increase the version number to release label Mar 18, 2026
@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request primarily focuses on a routine version update across multiple core packages to 0.8.2, ensuring consistency and reflecting recent changes. Concurrently, it modernizes the Docker build process for the physical_ai_server by updating repository references and streamlining service configurations. Additionally, a minor but important update was made to the rosbag_recorder's CMake configuration to align with current best practices.

Highlights

  • Version Bump: The version of several packages, including physical_ai_bt, physical_ai_interfaces, physical_ai_manager, physical_ai_server, physical_ai_tools, and rosbag_recorder, has been updated from 0.8.1 to 0.8.2.
  • Dockerfile Updates: The physical_ai_server Dockerfiles (Dockerfile.amd64 and Dockerfile.arm64) were updated to reference the talos_system_manager repository instead of the older talos repository, and the physical_ai_server-pipeline service was removed from the s6 user bundle.
  • CMake Modernization: The rosbag_recorder package's CMakeLists.txt was updated to use the more modern target_link_libraries command instead of ament_target_dependencies for linking rclcpp and rosbag2_cpp.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request primarily handles the version bump to 0.8.2 across multiple packages. The changes also include updating the talos repository to talos_system_manager in the Dockerfiles and removing the physical_ai_server-pipeline service from the s6 user bundle, which aligns with the PR description. I've made a couple of minor suggestions in the Dockerfiles to improve conciseness.

Comment thread physical_ai_server/Dockerfile.amd64
Comment thread physical_ai_server/Dockerfile.arm64
@robotpilot robotpilot merged commit 2e83400 into jazzy Mar 18, 2026
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bump Increase the version number to release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants