Skip to content

chore(release): pending libxmtp release#3712

Draft
github-actions[bot] wants to merge 1 commit into
mainfrom
release-plz/main
Draft

chore(release): pending libxmtp release#3712
github-actions[bot] wants to merge 1 commit into
mainfrom
release-plz/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Pending libxmtp release

Auto-generated changelog from conventional commits on main.
This PR is updated on every push and stays open. Merging it is
the "release" signal
— the release workflow then strips -dev,
tags vX.Y.Z, creates the GitHub Release hub, and fans out to the
SDKs. This PR contains ONLY changelog changes; the workspace
version is intentionally NOT bumped here.

🤖 Generated with Claude Code

@github-actions github-actions Bot requested a review from a team as a code owner June 3, 2026 21:34
@macroscopeapp

macroscopeapp Bot commented Jun 3, 2026

Copy link
Copy Markdown
Contributor

Approvability

Verdict: Needs human review

This PR adds a CHANGELOG.md file which is purely documentation. However, the file is owned by @xmtp/documentation and should be reviewed by that team.

You can customize Macroscope's approvability policy. Learn more.

@insipx insipx marked this pull request as draft June 3, 2026 21:36
@github-actions github-actions Bot force-pushed the release-plz/main branch from f941883 to c528e95 Compare June 3, 2026 22:14
insipx added a commit that referenced this pull request Jun 3, 2026
…3713)

Two changelog improvements, both stemming from the scruffy first
generated Release PR (#3712).

## 1. Tidy the generated changelog (`cliff.toml`)

**Body-dump scruff** — the template rendered `commit.message` (full
message = subject + body). GitHub squash-merges fill the commit body
with the PR description, so each merge dumped its whole PR body into the
changelog: Macroscope HTML-comment summary blocks, `Co-authored-by:`
trailers, even a pasted Nix build-error log (~316 of #3712's 461 lines).
```diff
-{{ commit.message | upper_first }}
+{{ commit.message | split(pat="\n") | first | trim | upper_first }}
```

**Fake per-scope groups** — non-conventional commits (e.g. `xmtp_proto:
…`, `bindings/mobile: …`) made git-cliff invent junk section headers
like `Xmtp_proto` / `Bindings/mobile`. A catch-all collects them into
one `Other` group:
```diff
+  { message = ".*", group = "<!-- 8 -->Other" },
```

Result (regenerated from `main`): group headers are exactly **Features ·
Bug Fixes · Performance · Documentation · Other**, every entry a clean
subject line, zero scruff.

## 2. Per-nightly changelog in the hub release (`release.yml`)

Each nightly hub GitHub Release now appends a **"Changes since the last
nightly"** section — the git-cliff delta over
`<previous-nightly-tag>..HEAD` (`--strip header`), computed before this
run is tagged so the newest existing `v*-nightly.*` tag is genuinely the
prior one. First-ever nightly (no prior nightly tag) falls back to
since-last-stable. Empty output is dropped. Adds git-cliff to the hub
job.

> Uses an explicit `<tag>..HEAD` range rather than the config's
stable-anchored `tag_pattern`, so it diffs against the last *nightly*,
not the last stable. Relies on the §1 fixes for clean output.

## Verification

- Regenerated changelog from `main`: clean, 5 well-formed groups, no
scruff.
- Simulated the per-nightly delta (`<tag>..HEAD --strip header`): clean
grouped output, 22 bullets, no header.
- All workflow YAML validated.

Once merged, the open Release PR (#3712) regenerates clean on the next
push to main, and the next real nightly carries a proper
since-last-nightly changelog.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- Macroscope's pull request summary starts here -->
<!-- Macroscope will only edit the content between these invisible
markers, and the markers themselves will not be visible in the GitHub
rendered markdown. -->
<!-- If you delete either of the start / end markers from your PR's
description, Macroscope will append its summary at the bottom of the
description. -->
> [!NOTE]
> ### Tidy generated changelog to show subject-only commits and group
non-conventional commits into 'Other'
> - Updates
[cliff.toml](https://github.com/xmtp/libxmtp/pull/3713/files#diff-e1372c8b03c40942b5d828a90975054cb8aaed3b38189f434396f922ec41a584)
to trim commit messages to their first line only and capitalise the
first character, removing multi-line noise from changelogs.
> - Adds a catch-all parser rule in
[cliff.toml](https://github.com/xmtp/libxmtp/pull/3713/files#diff-e1372c8b03c40942b5d828a90975054cb8aaed3b38189f434396f922ec41a584)
that places non-conventional commits into an 'Other' group instead of
creating per-scope groups.
> - Updates
[release.yml](https://github.com/xmtp/libxmtp/pull/3713/files#diff-87db21a973eed4fef5f32b267aa60fcee5cbdf03c67fafdc2a9b553bb0b15f34)
to install `git-cliff`, compute a delta changelog from the previous
nightly tag to `HEAD`, and append a
>
> <!-- Macroscope's review summary starts here -->
>
> <sup><a href="https://app.macroscope.com">Macroscope</a> summarized
eecd171.</sup>
> <!-- Macroscope's review summary ends here -->
>
<!-- macroscope-ui-refresh -->
<!-- Macroscope's pull request summary ends here -->

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@github-actions github-actions Bot force-pushed the release-plz/main branch 24 times, most recently from dab2b9f to 2bfba39 Compare June 9, 2026 01:11
@github-actions github-actions Bot force-pushed the release-plz/main branch 15 times, most recently from 0d591e5 to 7080dc9 Compare July 2, 2026 17:27
@github-actions github-actions Bot force-pushed the release-plz/main branch 11 times, most recently from 7f6c79f to 08ebdcb Compare July 9, 2026 17:02
@github-actions github-actions Bot force-pushed the release-plz/main branch 2 times, most recently from c45330b to 62e01eb Compare July 9, 2026 20:21
@github-actions github-actions Bot force-pushed the release-plz/main branch from 62e01eb to dc8f375 Compare July 9, 2026 23:05
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