Skip to content

chore: release v0.2.2#25

Open
jdx wants to merge 1 commit intomainfrom
release-plz-2026-02-15T13-21-30Z
Open

chore: release v0.2.2#25
jdx wants to merge 1 commit intomainfrom
release-plz-2026-02-15T13-21-30Z

Conversation

@jdx
Copy link
Owner

@jdx jdx commented Feb 15, 2026

🤖 New release

  • sigstore-verification: 0.2.1 -> 0.2.2 (✓ API compatible changes)
Changelog

0.2.2 - 2026-02-20

Fixed

  • generate Cargo.lock before security audit (#24)

Other

  • (deps) pin dependencies (#26)


This PR was generated with release-plz.


Note

Low Risk
Release metadata only (version/changelog) with no functional or runtime code changes.

Overview
Publishes release 0.2.2 by bumping the crate version in Cargo.toml.

Updates CHANGELOG.md with the 0.2.2 section, noting a fix to generate Cargo.lock before the security audit and dependency pinning work.

Written by Cursor Bugbot for commit d681f0e. This will update automatically on new commits. Configure here.

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @jdx, 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 0.2.2 for the sigstore-verification project. It includes an important fix related to the generation of the Cargo.lock file, ensuring it is created before any security audits are performed.

Highlights

  • New Release: Version 0.2.2 of the sigstore-verification crate has been released, incorporating a fix for generating Cargo.lock before security audits.
Changelog
  • CHANGELOG.md
    • Added entry for version 0.2.2, detailing a fix for generating Cargo.lock before security audit.
Activity
  • This pull request was automatically generated by release-plz to manage the release process.
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
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 the v0.2.2 release by updating the version in Cargo.toml and adding a corresponding entry to CHANGELOG.md. The changes are appropriate for a release. However, there appears to be an error with the release date in the changelog file, which I've commented on.

CHANGELOG.md Outdated

## [Unreleased]

## [0.2.2](https://github.com/jdx/sigstore-verification/compare/v0.2.1...v0.2.2) - 2026-02-15
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

The release date is set to a future date (2026-02-15). This is likely an error from the release automation and should be corrected to the actual release date.

@jdx jdx force-pushed the release-plz-2026-02-15T13-21-30Z branch from a022e74 to d681f0e Compare February 20, 2026 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant