Skip to content

chore: release v2.17.3#509

Merged
jdx merged 1 commit into
mainfrom
release
Feb 18, 2026
Merged

chore: release v2.17.3#509
jdx merged 1 commit into
mainfrom
release

Conversation

@mise-en-dev

Copy link
Copy Markdown
Collaborator

🐛 Bug Fixes

  • (publish) use gh api directly to create release with explicit tag_name by @jdx in #508

@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 formalizes the release of version 2.17.3, incorporating a critical bug fix related to the publishing process. The changes primarily involve updating version numbers across various configuration and documentation files to reflect the new release, ensuring consistency and proper tracking of the updated codebase.

Highlights

  • Release v2.17.3: This pull request officially releases version 2.17.3 of the project.
  • Bug Fix Included: The release incorporates a bug fix that addresses an issue with publishing, specifically by using the GitHub API directly to create releases with an explicit tag_name.
Changelog
  • CHANGELOG.md
    • Added entry for v2.17.3, detailing a bug fix for publishing releases.
  • Cargo.lock
    • Updated usage-cli and usage-lib versions to 2.17.3.
  • Cargo.toml
    • Updated usage-lib workspace dependency version to 2.17.3.
  • cli/Cargo.toml
    • Updated usage-cli package version to 2.17.3.
  • cli/usage.usage.kdl
    • Updated the usage-cli version to 2.17.3.
  • docs/cli/reference/commands.json
    • Updated the CLI version to 2.17.3.
  • docs/cli/reference/index.md
    • Updated the CLI version to 2.17.3.
  • lib/Cargo.toml
    • Updated usage-lib package version to 2.17.3.
Activity
  • No specific human activity (comments, reviews, or progress updates) has been recorded for this pull request since its creation.
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.

@jdx jdx enabled auto-merge (squash) February 18, 2026 13:29

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

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 is for releasing version 2.17.3. It includes version bumps in various files and an update to the changelog. The changes are appropriate for a release, but I found a small issue with the date in the changelog.

Comment thread CHANGELOG.md
@@ -1,5 +1,11 @@
# Changelog

## [2.17.3](https://github.com/jdx/usage/compare/v2.17.2..v2.17.3) - 2026-02-18

Copy link
Copy Markdown
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 year (2026), which appears to be a typo. This seems to be a recurring issue, as the previous release entry also has a future date. This might point to an issue in the script that generates the changelog.

@jdx jdx merged commit a18ba90 into main Feb 18, 2026
6 checks passed
@jdx jdx deleted the release branch February 18, 2026 13:30
@codecov

codecov Bot commented Feb 18, 2026

Copy link
Copy Markdown

Codecov Report

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

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #509   +/-   ##
=======================================
  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.

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