Skip to content

Conversation

@Pr0methean
Copy link
Member

πŸ€– New release

  • zip: 4.3.0 -> 4.4.0 (βœ“ API compatible changes)
Changelog

4.4.0 - 2025-08-21

πŸš€ Features

  • Add lzma-static and xz-static features that enable liblzma/static (#393)

βš™οΈ Miscellaneous Tasks

  • Move deprecated annotations to fix a Clippy warning (#391)


This PR was generated with release-plz.

@amazon-q-developer
Copy link
Contributor

⏳ I'm reviewing this pull request for security vulnerabilities and code quality issues. I'll provide an update when I'm done

Copy link
Contributor

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

Summary of Changes

Hello @Pr0methean, 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 performs a routine release, updating the zip crate to version 4.4.0. The update introduces new features for static LZMA and XZ compression support and includes a minor code quality improvement by addressing a Clippy warning related to deprecated annotations. This is an API-compatible change, ensuring seamless integration for existing users.

Highlights

  • Version Update: The zip crate has been updated from version 4.3.0 to 4.4.0.
  • New Features: New lzma-static and xz-static features have been added to enable liblzma/static support.
  • Code Quality: Deprecated annotations were moved to resolve a Clippy warning, improving code quality.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

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

@amazon-q-developer
Copy link
Contributor

βœ… I finished the code review, and didn't find any security or code quality issues.

Copy link
Contributor

@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 prepares for the v4.4.0 release by updating the version in Cargo.toml and adding release notes to CHANGELOG.md. The changes are appropriate for a release, but I've identified a minor formatting issue in the changelog where a heading is duplicated, likely due to the release automation tool.

Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com>
@Pr0methean Pr0methean enabled auto-merge August 21, 2025 04:54
@Pr0methean Pr0methean added this pull request to the merge queue Aug 21, 2025
Merged via the queue into master with commit f4a618d Aug 21, 2025
77 checks passed
@Pr0methean Pr0methean deleted the release-plz-2025-08-21T04-47-33Z branch August 21, 2025 09:25
cosmicexplorer pushed a commit to cosmicexplorer/zip2 that referenced this pull request Sep 30, 2025
* chore: release v4.4.0

* Remove duplicate main header from CHANGELOG.md

Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com>

---------

Signed-off-by: Chris Hennick <4961925+Pr0methean@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants