v9.2.0

[mike-hunhoff]

Release checklist

• Ensure all milestoned issues/PRs are addressed, or reassign to a new milestone.
• Add the don't merge label to all PRs that are close to be ready to merge (or merge them if they are ready) in capa and capa-rules.
• Ensure the CI workflow succeeds in master.
• Ensure that python scripts/lint.py rules/ --thorough succeeds (only missing examples offenses are allowed in the nursery). You can manually trigger a thorough lint in CI via the "Run workflow" option.
  • https://github.com/mandiant/capa-rules/actions/runs/15426844128
• Review changes
  • capa https://github.com/mandiant/capa/compare/\<last-release>...master
  • capa-rules https://github.com/mandiant/capa-rules/compare/\...master
• Update CHANGELOG.md
• Update capa/version.py
• Create a PR with the updated CHANGELOG.md and capa/version.py. Copy this checklist in the PR description.
• Update the homepage (i.e. What's New section)
• After PR review, merge the PR and create the release in GH using text from the CHANGELOG.md.
• Verify GH actions
  • upload artifacts
  • publish to PyPI
  • create tag in capa rules
  • create release in capa rules
• Spread the word
• Update internal service

[gemini-code-assist]

Hello @mike-hunhoff, 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!

Summary of Changes

Hello team,

gemini-code-assist here, providing a summary of this pull request to help everyone quickly understand the changes and context.

This pull request is focused on preparing the repository for the v9.2.0 release. The changes involve updating the version number, documenting the release contents in the CHANGELOG.md, and adding the release notes to the project's website (index.html). It follows the standard procedure for cutting a new release.

Highlights

• Version Update: The core capa version string in capa/version.py has been updated from 9.1.0 to 9.2.0.
• Changelog Documentation: A new section for v9.2.0 has been added to CHANGELOG.md. This includes the release description, moves the vmray feature enhancement from the master (unreleased) section to the v9.2.0 section, and updates the raw diff links to compare against the new v9.2.0 tag.
• Website Release Notes: The project's website (web/public/index.html) has been updated to include a dedicated section for the v9.2.0 release notes under the "Tool Updates" section.

Changelog

• CHANGELOG.md
  • Added a new section header for v9.2.0.
  • Moved the vmray: do not restrict analysis to PE and ELF files feature entry from the master (unreleased) section to the new v9.2.0 section.
  • Added the release description paragraph for v9.2.0.
  • Updated the raw diff links to compare capa and capa-rules against the v9.2.0 tag instead of master.
• capa/version.py
  • Updated the __version__ string from "9.1.0" to "9.2.0".
• web/public/index.html
  • Added a new <h3> and <p> block for v9.2.0 release notes within the "Tool Updates" section.

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 is currently in preview and 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 to provide feedback.

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.

---

Version number bumps,
Changelog gets new entries,
Release is coming.

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 v9.2.0 release by updating the CHANGELOG.md, capa/version.py, and web/public/index.html files. The changes are well-structured and align with the release checklist.

One point of attention is the release date specified in index.html, which appears to be set far in the future. Please see the specific comment on that file.

Summary of Findings

• Release Date in Homepage: The release date for v9.2.0 on web/public/index.html is set to 2025-06-03. This date should be confirmed or corrected if it's a placeholder and the release is sooner. (Commented)
• Changelog Placeholder Inconsistency: In CHANGELOG.md, the ## master (unreleased) section uses a - placeholder under ### New Rules (0), while other empty sections in the same block (like ### New Features) are simply left blank. This is a minor stylistic inconsistency. (Not commented due to severity settings)

Merge Readiness

The pull request is well-prepared for the v9.2.0 release. However, there is one medium-severity issue regarding the release date on the homepage (web/public/index.html) that should be clarified or addressed before merging. Once this is resolved, the PR should be ready. As an AI, I am not authorized to approve pull requests; please ensure further review and approval by authorized maintainers.