chore: release v8.3.0

[Pr0methean]

🤖 New release

• zip: 8.2.0 -> 8.3.0

Changelog

8.3.0 - 2026-03-19

🚀 Features

• add must_use (#727)
• improve and fix extended timestamp extra field parsing (#713)
• add crc32 ignore option (#710)
• path related code in single file (#712)

🐛 Bug Fixes

• Malformed ZIP64 file output (#715) (#717)

🚜 Refactor

• refactor some imports (#734)
• move code to distinct file (datetime, FixedSizeBlock) (#733)
• move stream code to src/read/stream.rs (#731)
• remove zip64 extra field update (#732)
• improve part of the code with clippy help (#725)
• simplify code for unicode extra field and improve error message (#724)
• reorganize code (#714)

Deps

• avoid pulling in zeroize_derive (#720)

---

This PR was generated with release-plz.

[gemini-code-assist]

Summary of Changes

Hello, 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 officially releases version 8.3.0 of the zip crate. It incorporates a series of new features, addresses a critical bug related to ZIP64 file output, and includes several code quality improvements and refactorings to enhance maintainability and performance. The release ensures API compatibility with the previous version.

Highlights

• Features: Added a must_use attribute, improved and fixed extended timestamp extra field parsing, introduced a CRC32 ignore option, and consolidated path-related code into a single file.
• Bug Fixes: Resolved an issue causing malformed ZIP64 file output.
• Refactoring: Improved code quality with Clippy suggestions, simplified code for unicode extra fields, enhanced error messages, and reorganized the codebase.
• Dependencies: Updated dependencies to avoid pulling in zeroize_derive.

Changelog

• CHANGELOG.md
  • Added release notes for version 8.3.0, detailing new features, bug fixes, refactorings, and dependency updates.
• Cargo.toml
  • Updated the package version from 8.2.0 to 8.3.0.

Activity

• The pull request was created by Pr0methean to release version 8.3.0 of the zip crate. No further human activity (comments, reviews) has been recorded yet.

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 contains a critical date error that must be fixed before merge.

Critical Issue

The release date is set to 2026-03-17, which is one year in the future. This needs to be corrected to today's actual date (2025-03-17).

Review Summary

The version bump from 8.2.0 to 8.3.0 is appropriate given the changes include new features, bug fixes, and refactors without breaking changes. The CHANGELOG format follows the Keep a Changelog standard correctly. Once the date is corrected, this release can proceed.

---

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 pull request prepares for the v8.3.0 release. It updates the version in Cargo.toml and adds the corresponding release notes to CHANGELOG.md. The changes are consistent and appear correct for a release.

[Its-Just-Nans]

Full diff is ff001c6...release-plz-2026-03-17T16-54-48Z

I think we can merge it tomorrow