chore: release v7.3.0

[Pr0methean]

🤖 New release

• zip: 7.3.0-pre1 -> 7.3.0

Changelog

7.3.0 - 2026-02-02

🚀 Features

• cleanup the benchs and Cargo.toml (#606)
• Add support for per-file comments (#543)

🐛 Bug Fixes

• Return an error if abort_file() fails when exceeding non-large-file limit (#598)

⚙️ Miscellaneous Tasks

• Bump version to 7.3.0 (semver checks fail if it's still 7.3.0-pre1)

---

This PR was generated with release-plz.

[gemini-code-assist]

Summary of Changes

Hello @Pr0methean, 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 performs a routine release chore, updating the zip crate to its stable 7.3.0 version. This release integrates a new capability for per-file comments and addresses a technical requirement to ensure proper semantic versioning compliance.

Highlights

• Version Bump: The zip crate has been updated from 7.3.0-pre1 to 7.3.0, finalizing the release.
• New Feature: Version 7.3.0 introduces support for per-file comments within zip archives.
• Miscellaneous Task: The version bump was also necessary to resolve semantic versioning check failures that occurred while it was still 7.3.0-pre1.

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

[amazon-q-developer]

This release PR looks good. The changelog entry is properly formatted following Keep a Changelog standards, the PR title conforms to Conventional Commits format, and the version bump from 7.3.0-pre1 to 7.3.0 is appropriate for a stable release. The changes are minimal and focused solely on release documentation without introducing any functional code changes.

---

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.

[gemini-code-assist]

Code Review

This is an automated release pull request for version 7.3.0. The only change is the addition of the release notes for this version to the CHANGELOG.md file. The update is consistent with the project's changelog format and accurately reflects the new release. I find no issues with this change.

[Pr0methean]

Waiting on #596, #600, #601, and any other findings in https://github.com/zip-rs/zip2/security/quality/ai-findings that might be useful to merge. I'd also like to do another zizmor run and another StepSecurity run after #596 is merged, and repeat if necessary until neither of them raises any issues about the other's changes, before the release.

[stepsecurity-app]

Security Policy Alert: Actions Policy Violation

This workflow run has been blocked by StepSecurity's actions policy because it uses actions that are not allowed by your organization's policy.

Disallowed Actions:

• step-security/dependabot-fetch-metadata@38d404f7e1742ae1cfa9b25ade9afa0c7a288e77

To fix this issue, please modify the workflow to use only allowed actions. Contact your organization administrator to request changes to the allowed actions list if needed.

For more information, see StepSecurity's Actions Policy documentation.