Skip to content

chore(deps): bump communique to 1.0.3#246

Merged
jdx merged 1 commit intomainfrom
bump-communique-1.0.3
Apr 23, 2026
Merged

chore(deps): bump communique to 1.0.3#246
jdx merged 1 commit intomainfrom
bump-communique-1.0.3

Conversation

@jdx
Copy link
Copy Markdown
Contributor

@jdx jdx commented Apr 23, 2026

Summary

Refreshes mise.lock's communique entry from 1.0.2 → 1.0.3 so enhance-release picks up the UTF-8 char-boundary fix from jdx/communique#113.

The prior truncation sliced release bodies at byte 3072 with no regard for UTF-8 char boundaries, which crashed enhance-release for aube v1.0.0 because one of the recent-release style samples had an em-dash straddling the cutoff.

Test plan

  • Refreshed URLs, checksums, and asset IDs for all 6 platforms in the existing [[tools.communique]] block
  • CI green on the enhance-release job for the next tag

🤖 Generated with Claude Code


Note

Low Risk
Low risk: lockfile-only dependency bump updating download URLs/checksums/asset IDs, with no runtime code changes.

Overview
Bumps the pinned communique tool in mise.lock from 1.0.2 → 1.0.3, updating the associated per-platform download URLs, checksums, and GitHub asset IDs.

Reviewed by Cursor Bugbot for commit d78a7d4. Bugbot is set up for automated code reviews on this repo. Configure here.

Brings in the UTF-8 char-boundary fix for release-note truncation
(jdx/communique#113), which crashed enhance-release for aube v1.0.0
because the prior em-dash in a recent release body straddled the
3072-byte cutoff.

Co-Authored-By: Claude Opus 4.7 (1M context) <[email protected]>
@greptile-apps
Copy link
Copy Markdown

greptile-apps Bot commented Apr 23, 2026

No reviewable files after applying ignore patterns.

@jdx jdx merged commit b170aa3 into main Apr 23, 2026
14 checks passed
@jdx jdx deleted the bump-communique-1.0.3 branch April 23, 2026 20:59
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