Skip to content

chore: release v2.17.2#507

Merged
jdx merged 1 commit intomainfrom
release
Feb 18, 2026
Merged

chore: release v2.17.2#507
jdx merged 1 commit intomainfrom
release

Conversation

@mise-en-dev
Copy link
Copy Markdown
Collaborator

🐛 Bug Fixes

  • (publish) anchor gh release create to GITHUB_SHA to avoid untagged release by @jdx in #506

@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @mise-en-dev, 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 primarily constitutes a patch release, bumping the project version to v2.17.2. The core change addresses a specific issue where GitHub releases were occasionally created without proper tags, ensuring that future releases are correctly anchored to their respective commit SHAs. This update propagates the new version number throughout the project's configuration, dependency locks, and documentation.

Highlights

  • Version Bump: The project's version has been updated to v2.17.2 across all relevant configuration and documentation files.
  • Bug Fix: A bug related to untagged GitHub releases has been addressed by anchoring the gh release create command to GITHUB_SHA.
  • Changelog Update: The CHANGELOG.md file has been updated to reflect the new v2.17.2 release and its associated bug fix.
Changelog
  • CHANGELOG.md
    • Added new changelog entries for version 2.17.2.
  • Cargo.lock
    • Updated usage-cli and usage-lib package versions to 2.17.2.
  • Cargo.toml
    • Updated usage-lib workspace dependency version to 2.17.2.
  • cli/Cargo.toml
    • Updated the usage-cli package version to 2.17.2.
  • cli/usage.usage.kdl
    • Updated the usage-cli version to 2.17.2.
  • docs/cli/reference/commands.json
    • Updated the version field to 2.17.2.
  • docs/cli/reference/index.md
    • Updated the displayed version to 2.17.2.
  • lib/Cargo.toml
    • Updated the usage-lib package version to 2.17.2.
Activity
  • No human activity (comments, reviews) has been recorded on this pull request 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.

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

This pull request handles the release of version v2.17.2. The changes consist of version bumps in various manifest and documentation files to reflect the new version, and the changelog has been updated accordingly. The changes are consistent with a standard release process and appear to be correct.

@codecov
Copy link
Copy Markdown

codecov Bot commented Feb 18, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 77.88%. Comparing base (e3243cc) to head (bd93cc7).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #507   +/-   ##
=======================================
  Coverage   77.88%   77.88%           
=======================================
  Files          48       48           
  Lines        6660     6660           
  Branches     6660     6660           
=======================================
  Hits         5187     5187           
  Misses       1109     1109           
  Partials      364      364           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jdx jdx merged commit 5539449 into main Feb 18, 2026
8 checks passed
@jdx jdx deleted the release branch February 18, 2026 13:07
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.

2 participants