Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: jdx/usage
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.17.4
Choose a base ref
...
head repository: jdx/usage
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.18.0
Choose a head ref
  • 2 commits
  • 9 files changed
  • 3 contributors

Commits on Feb 18, 2026

  1. feat(publish): extract communique into separate enhance-release job (#…

    …513)
    
    ## Summary
    
    - Moves `communique generate` out of the `release` job into a dedicated
    `enhance-release` job that runs after `release`
    - Since it's a separate job, it can be re-run independently from the
    GitHub Actions UI if it fails (e.g. Anthropic rate limits, transient API
    errors)
    - Runs after `gh release edit --draft=false` so the release is published
    and visible to communique
    
    ## Test plan
    
    - [ ] Trigger a tag push and verify `enhance-release` appears as a
    separate job in the workflow run
    
    🤖 Generated with [Claude Code](https://claude.com/claude-code)
    
    <!-- CURSOR_SUMMARY -->
    ---
    
    > [!NOTE]
    > **Low Risk**
    > Only adjusts GitHub Actions job orchestration; no application/runtime
    code changes, with the main risk being altered release workflow
    timing/dependencies.
    > 
    > **Overview**
    > Moves release-note enhancement (`communique generate ...
    --github-release`) out of the release creation flow into a new
    `enhance-release` job that runs after `release`.
    > 
    > This makes the AI-backed release-notes step independent/re-runnable
    and ensures it runs against the published release (adds `fetch-depth: 0`
    to the checkout in that job).
    > 
    > <sup>Written by [Cursor
    Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
    379d1d0. This will update automatically
    on new commits. Configure
    [here](https://cursor.com/dashboard?tab=bugbot).</sup>
    <!-- /CURSOR_SUMMARY -->
    
    ---------
    
    Co-authored-by: Claude Sonnet 4.6 <[email protected]>
    jdx and claude authored Feb 18, 2026
    Configuration menu
    Copy the full SHA
    c30745c View commit details
    Browse the repository at this point in the history
  2. chore: release v2.18.0 (#514)

    ### 🚀 Features
    
    - **(publish)** extract communique into separate enhance-release job by
    [@jdx](https://github.com/jdx) in
    [#513](#513)
    mise-en-dev authored Feb 18, 2026
    Configuration menu
    Copy the full SHA
    8b35fc3 View commit details
    Browse the repository at this point in the history
Loading