rel v0.8.0 & Update dependencies in Cargo.toml

[isdaniel]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @isdaniel, I'm Gemini Code Assist¹! 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 version increment for the pg2any_lib crate to 0.8.0 and a comprehensive update of project dependencies. These changes ensure the project leverages the latest features, bug fixes, and security improvements from its underlying libraries, maintaining compatibility and stability within the Rust ecosystem.

Highlights

• pg2any_lib Version Bump: The pg2any_lib crate has been updated from version 0.7.0 to 0.8.0.
• Dependency Updates: Numerous dependencies in Cargo.toml and Cargo.lock have been upgraded to their latest versions, including chrono, bytes, thiserror, tracing, flate2, hyper, and hyper-util.

🧠 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.

Changelog

• Cargo.lock
  • Updated flate2 from 1.1.5 to 1.1.9.
  • Updated hyper-util from 0.1.19 to 0.1.20 and removed its futures-core dependency.
  • Updated pg2any_lib from 0.7.0 to 0.8.0.
  • Updated system-configuration from 0.6.1 to 0.7.0.
• Cargo.toml
  • Updated chrono from 0.4.42 to 0.4.44.
  • Updated bytes from 1.11.0 to 1.11.1.
  • Updated thiserror from 2.0.12 to 2.0.18.
  • Updated tracing from 0.1.41 to 0.1.44.
  • Updated tracing-subscriber from 0.3.20 to 0.3.22.
  • Updated flate2 from 1.1.5 to 1.1.9.
  • Updated hyper from 1.7 to 1.8.1.
  • Updated hyper-util from 0.1.16 to 0.1.20.
  • Updated pg2any_lib from 0.7.0 to 0.8.0.
• pg2any-lib/Cargo.toml
  • Updated the package version from 0.7.0 to 0.8.0.

Activity

• No human activity recorded for this pull request.

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.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

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. ↩

[gemini-code-assist]

Code Review

This pull request prepares for the v0.8.0 release by bumping the version of the pg2any-lib crate and updating several dependencies. While the dependency updates are mostly routine, I've found a critical issue with the thiserror dependency, which points to a yanked version of the crate. This could cause build failures and should be addressed. For future release pull requests, it would be very helpful to include a summary of changes or a link to a changelog in the description to provide context for the version bump.