Update python.yaml

[Bernie-mirsee]

Please add the following dependency to the rosdep database.

Package name:

piper-tts

Package Upstream Source:

https://github.com/rhasspy/piper

Purpose of using this:

Piper is a general-purpose text-to-speech engine, which is useful for providing speech output in ROS.

Distro packaging links:

https://pypi.org/project/piper-tts/

[github-actions]

Thanks for sending a pull request to ROS distro!

This is an automated tool that helps check your pull request for correctness.
This tool checks a number of attributes associated with your ROS package and generates a report that helps our reviewers merge your pull request in a timely fashion. Here are a few things to consider when sending adding or updating a package to ROS Distro.
ROS Distro includes a very helpful CONTRIBUTING.md file that we recommend reading if it is your first time submitting a package.
Please also read the ROS Distro review guidelines which summarizes this release process.

ROS Distro Considerations

• ROS Distributions are created using REP-134 Standards Track as a guide.
• Your package name should comply to REP-144 ROS Package Naming
• Your package must build for all platforms and architectures on the ROS buildfarm. See REP-2000 ROS Releases and Supported Platforms for all supported platforms for your ROS Distro.
• Your package must contain an OSI approved license. Your package.xml file must also include that license in a machine readable format. See REP-149 Package Manifest Format Three Specification for additional details.
• A publicly available, open source, repository for your ROS package.
• While not required, we recommend that you create an account for ROS Discourse and subscribe to the appropriate release topic.
• If you would like, you may join our Zulip Server and ask questions in the Infrastructure General channel.

Package Considerations

Having your package included in a ROS Distro is a badge of quality, and we recommend that package developers strive to create packages of the highest quality. We recommend package developers review the following resources before submitting their package.

• REP-2004 Package Quality Declaration-- The ROS 2 TSC has created a quality rating system for ROS packages. These ratings should serve as a guide for package developers. We recommend package developers achieve a quality level of three or higher.
• Documentation -- it is recommended that ROS packages include an extensive README.md file, and API level documentation using the Sphinx documentation system.
• Maintainer Responsibilities -- the ROS 2 documentation includes a guide to ROS package maintainer responsibilities that summarizes your responsibilities as an open source maintainer. While we do not enforce these requirements on package maintainers they should be considered best practices.
• We recommend that your package should strive to conform to the ROS 2 Developer Guide and the ROS 2 Style Guide.

Need Help?

Please post your questions to Robotics Stack Exchange or refer to the Infrastructure General channel on our Zulip server.

---

For changes related to rosdep:

• ❌ There are problems with the names of new rosdep keys:
  • Keys which contain only pip rules should end in '-pip'
• ✅ Platforms for new rosdep rules are valid
• ✅ Installers for new rosdep rules are valid
• ✅ New keys appear suitable for rosdep
• 📝 Disclaimer: Pip-only rules cannot be used by packages on the ROS buildfarm

For changes related to yamllint:

• ❌ One or more linter violations were added to YAML files

Previous automated review is stale

[dave-mirsee]

Are some checks stuck? Can this be closed?

[mergify]

Tick the box to add this pull request to the merge queue (same as @mergifyio queue).

• Queue this pull request

[Bernie-mirsee]

Okay, done.

…

On Mon, Jun 29, 2026 at 11:50 AM mergify[bot] ***@***.***> wrote: *mergify[bot]* left a comment (ros/rosdistro#51971) <#51971 (comment)> Tick the box to add this pull request to the merge queue (same as @Mergifyio queue). - Queue this pull request — Reply to this email directly, view it on GitHub <#51971?email_source=notifications&email_token=CFSZR7F3XIKBUFVAP6PLGHD5CKF3FA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBTGQ2DENJYGI22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L#issuecomment-4834425825>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CFSZR7HXKWOVQHTWAD74ISD5CKF3FAVCNFSNUABDKJSXA33TNF2G64TZHMZTCNBZHA2DKO2JONZXKZJ3GQ3DENJRGUYDQNRWUF3AE> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/CFSZR7AS6QPZW7JZZDDUMOL5CKF3FA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBTGQ2DENJYGI22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2KUZTPN52GK4S7NFXXG> and Android <https://github.com/notifications/mobile/android/CFSZR7ET7IEPEU7T6CX5TX35CKF3FA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOBTGQ2DENJYGI22M4TFMFZW63VGMF2XI2DPOKSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>. Download it today! You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Bernie Roehl Senior Software Engineer Mirsee Robotics Inc. #203-485 Pinebush Road, Cambridge, ON, N1T 0A6 1-855-472-3309 |

-- The information in this email is intended only for the named recipient and may be privileged or confidential. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this email in error, please notify us immediately by returning it to the sender and delete this copy from your system. As e-mails are susceptible to alteration, Mirsee Robotics shall not be liable for the message if altered, changed or falsified.

[github-actions]

For changes related to rosdep:

• ✅ New rosdep keys are named appropriately
• ✅ New keys appear suitable for rosdep
• 📝 Disclaimer: Pip-only rules cannot be used by packages on the ROS buildfarm

For changes related to yamllint:

• ✅ All new lines of YAML pass linter checks