Skip to content

chore: release v2.18.0#514

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

chore: release v2.18.0#514
jdx merged 1 commit intomainfrom
release

Conversation

@mise-en-dev
Copy link
Collaborator

🚀 Features

  • (publish) extract communique into separate enhance-release job by @jdx in #513

@gemini-code-assist
Copy link

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 finalizes the release of version 2.18.0 for the 'usage' project. It primarily updates version numbers across various configuration and documentation files to reflect the new release. A key feature included in this release is the refactoring of the release process to extract communique generation into a dedicated 'enhance-release' job.

Highlights

  • New Release: Version 2.18.0 has been released, incorporating a new feature.
  • Release Process Enhancement: The communique extraction has been moved into a separate 'enhance-release' job.
Changelog
  • CHANGELOG.md
    • Added a new entry for version 2.18.0, detailing the feature of extracting communique into a separate 'enhance-release' job.
  • Cargo.lock
    • Updated the 'usage-cli' package version to 2.18.0.
    • Updated the 'usage-lib' package version to 2.18.0.
  • Cargo.toml
    • Updated the 'usage-lib' workspace dependency version to 2.18.0.
  • cli/Cargo.toml
    • Updated the 'usage-cli' package version to 2.18.0.
  • cli/usage.usage.kdl
    • Updated the 'usage-cli' version to 2.18.0.
  • docs/cli/reference/commands.json
    • Updated the 'version' field to 2.18.0.
  • docs/cli/reference/index.md
    • Updated the displayed version to 2.18.0.
  • lib/Cargo.toml
    • Updated the 'usage-lib' package version to 2.18.0.
Activity
  • No specific activity (comments, reviews) was recorded for this pull request.
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.

@codecov
Copy link

codecov bot commented Feb 18, 2026

Codecov Report

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

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

Copy link

@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 for the release of v2.18.0. The changes primarily consist of version bumps in various configuration and generated files, along with an update to the CHANGELOG.md. My review identified a minor issue with the release date in the changelog that should be corrected for accuracy.

@@ -1,5 +1,11 @@
# Changelog

## [2.18.0](https://github.com/jdx/usage/compare/v2.17.4..v2.18.0) - 2026-02-18

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-18). This seems to be a recurring issue, as previous recent releases also have dates in 2025 and 2026. This might be due to a misconfiguration in the release automation. Using the correct, current date for releases would prevent confusion for users tracking the project's timeline.

@jdx jdx merged commit 8b35fc3 into main Feb 18, 2026
8 checks passed
@jdx jdx deleted the release branch February 18, 2026 14:46
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

Comments