Skip to content

chore: release v8.2.0#678

Merged
Pr0methean merged 1 commit intomasterfrom
release-plz-2026-02-17T19-12-20Z
Mar 3, 2026
Merged

chore: release v8.2.0#678
Pr0methean merged 1 commit intomasterfrom
release-plz-2026-02-17T19-12-20Z

Conversation

@Pr0methean
Copy link
Copy Markdown
Member

@Pr0methean Pr0methean commented Feb 17, 2026

🤖 New release

  • zip: 8.1.0 -> 8.2.0 (✓ API compatible changes)
Changelog

8.2.0 - 2026-03-02

🚀 Features

  • allow custom salt (#680)
  • Support compressing bzip2 when feature bzip2-rs is enabled, since bzip2/bzip2-sys now supports it (#685)
  • enforce clippy in CI (#674)

🐛 Bug Fixes

  • zip64 central header (issue 617) (#629)
  • allow aes password as bytes (#686)
  • handle extra field padding (#682)

🚜 Refactor

  • Simplify 2 type conversions in src/write.rs (#687)

⚡ Performance

  • AI tweaks for string type conversions in src/types.rs (#670)


This PR was generated with release-plz.

@gemini-code-assist
Copy link
Copy Markdown
Contributor

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 automates the release of version 8.1.1 for the zip crate. The update primarily incorporates a performance enhancement related to string type conversions, ensuring the library remains efficient while maintaining API compatibility.

Highlights

  • New Release: The zip crate has been updated from version 8.1.0 to 8.1.1, signifying API compatible changes.
  • Performance Improvement: A performance tweak related to AI for string type conversions in src/types.rs has been included in this release.
Changelog
  • CHANGELOG.md
    • Added a new changelog entry for version 8.1.1, detailing a performance improvement for string type conversions.
  • Cargo.toml
    • Updated the package version of the zip crate from 8.1.0 to 8.1.1.
Activity
  • This pull request was automatically generated by release-plz to publish a new version of the zip crate.
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.

Copy link
Copy Markdown
Contributor

@amazon-q-developer amazon-q-developer bot left a comment

Choose a reason for hiding this comment

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

This release PR correctly updates the version from 8.1.0 to 8.1.1 and adds the corresponding CHANGELOG entry. The version numbers are consistent across files, and the CHANGELOG follows the standard format with proper references to the performance improvements from PR #670. The PR title conforms to Conventional Commits requirements.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

Copy link
Copy Markdown
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

The pull request is a standard release update for version 8.1.1. It correctly bumps the version in Cargo.toml and adds the corresponding entry to CHANGELOG.md. The changes are consistent with the PR title and description. No issues were found in the provided diff.

@Pr0methean Pr0methean changed the title chore: release v8.1.1 chore: release v8.2.0 Feb 17, 2026
@Pr0methean Pr0methean force-pushed the release-plz-2026-02-17T19-12-20Z branch 8 times, most recently from fd9f8cf to 2d0ce0e Compare February 22, 2026 04:13
@Pr0methean Pr0methean force-pushed the release-plz-2026-02-17T19-12-20Z branch 11 times, most recently from 2c7e1b3 to 4bd16da Compare March 2, 2026 09:19
@Pr0methean Pr0methean force-pushed the release-plz-2026-02-17T19-12-20Z branch from 4bd16da to 9e08c51 Compare March 2, 2026 15:49
@Pr0methean Pr0methean added this pull request to the merge queue Mar 3, 2026
Merged via the queue into master with commit ff001c6 Mar 3, 2026
130 checks passed
@Pr0methean Pr0methean deleted the release-plz-2026-02-17T19-12-20Z branch March 3, 2026 04:19
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.

1 participant