v1.0.3: UTF-8 boundary fix + rustls-webpki security bump#108
Conversation
1747562 to
2e47175
Compare
There was a problem hiding this comment.
Code Review
This pull request bumps the version of the communique package from 1.0.2 to 1.0.3 across Cargo.toml, Cargo.lock, and the CHANGELOG.md. Feedback was provided regarding an inaccurate changelog entry that claims dependencies were updated when only the package version itself was changed.
| ## Fixed | ||
|
|
||
| - Retry malformed `submit_release_notes` tool calls instead of aborting the run, with a cap of 3 attempts ([#105](https://github.com/jdx/communique/pull/105)) | ||
| - Bump `rustls-webpki` to 0.103.13 to address [RUSTSEC-2026-0104](https://rustsec.org/advisories/RUSTSEC-2026-0104) (reachable panic in CRL parsing) ([#107](https://github.com/jdx/communique/pull/107)) |
There was a problem hiding this comment.
The changelog entry - update Cargo.lock dependencies appears to be inaccurate for this release. The provided diff for Cargo.lock shows that only the communique package version itself was bumped from 1.0.2 to 1.0.3, with no changes to any other dependencies. If no dependencies were actually updated, this entry should be removed or corrected to reflect the actual changes in this version.
2e47175 to
0437b4f
Compare
0437b4f to
7f85448
Compare
Greptile SummaryRelease-plz–generated PR that cuts Confidence Score: 5/5Safe to merge — purely release bookkeeping with no functional code changes. All six changed files are version-string or changelog updates only. Version is consistent across every artifact. The new 1.0.3 changelog block is properly formatted. No logic, dependencies, or API surface changed in this PR. No files require special attention. Important Files Changed
Flowchart%%{init: {'theme': 'neutral'}}%%
flowchart TD
A[release-plz detects merged PRs] --> B[Bumps version: 1.0.2 → 1.0.3]
B --> C[Cargo.toml]
B --> D[Cargo.lock]
B --> E[communique.usage.kdl]
B --> F[docs/cli/commands.json]
B --> G[docs/cli/index.md]
B --> H[CHANGELOG.md]
H --> H1[Added 1.0.3 section\nFixed: UTF-8 truncation\nOther: banner improvements]
Reviews (6): Last reviewed commit: "[autofix.ci] apply automated fixes" | Re-trigger Greptile |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #108 +/- ##
=======================================
Coverage 94.11% 94.11%
=======================================
Files 26 26
Lines 4076 4076
Branches 4076 4076
=======================================
Hits 3836 3836
Misses 155 155
Partials 85 85 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
7f85448 to
00b757f
Compare
44ba84e to
0b77e7c
Compare
bff8027 to
5ef9fa2
Compare
5ef9fa2 to
cd979a8
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit cd979a8. Configure here.
cd979a8 to
4a15a22
Compare
8b93585 to
85f9e32
Compare

A small patch release that fixes a panic when generating notes against releases with multi-byte characters in their bodies, and picks up a security fix in
rustls-webpki.Fixed
communique generatetruncates each recent release body to 3072 bytes to keep the prompt small, but previously sliced&body[..3072]directly. If byte 3072 fell inside a multi-byte UTF-8 character (common with em-dashes, which are 3 bytes), the command would panic withbyte index 3072 is not a char boundary. The truncation now walks back to the nearest char boundary before slicing, with a regression test covering the case. (#113) (@jdx)Security
rustls-webpkibumped to 0.103.13 — Addresses RUSTSEC-2026-0104, a reachable panic in certificate revocation list parsing. Lockfile-only change. (#107) (@jdx)Docs
ResizeObserver-based height syncing so VitePress's nav offset stays correct on resize. (#109, #110, #111, #112) (@jdx)