ci(clients): Release the Python and Rust clients separately (#729)

Splits the shared client release into one Craft release per client, each
with its own changelog. A PR that changes both clients now shows up in
both changelogs, and the title scope no longer decides anything.

## What changes

- **Two release units:** `clients/python/.craft.yml` and
`clients/rust/.craft.yml`, with separate tag prefixes (`py-client@` /
`rs-client@`), release branches (`release-py/` / `release-rust/`) and
bump scripts.
- **One release workflow** with a `python`/`rust` input. The Python
build workflow is now `build-python-client.yml`.
- **Changelogs grouped by type** (Breaking, Features, Fixes, Other) in
each client's `.github/release.yml` (two identical copies; Craft only
reads the one next to `.craft.yml`). Other Changes catches everything
else as a patch bump.
- **Per-client changelogs:** `clients/CHANGELOG.md` is split into
`clients/python/CHANGELOG.md` and `clients/rust/CHANGELOG.md` in the new
format. Each keeps only entries for PRs that changed that client's
directory.
- **Two changelog previews**, one per client, reported as checks instead
of PR comments so they don't overwrite each other.
- `AGENTS.md` no longer asks for client scopes.

## Before the first release

Craft finds the previous release from the latest tag with the client's
prefix. Without a starting tag, the first changelog would contain the
whole history. Seed both prefixes at `0.2.10`:

```sh
git tag py-client@0.2.10 0.2.10
git tag rs-client@0.2.10 0.2.10
git push origin py-client@0.2.10 rs-client@0.2.10
```

## Things to know

- A `### Changelog Entry` section applies to every client the PR
touches. If a PR touches both clients but the custom text only makes
sense for one, it shows up in the other changelog too. For example, #704
changed both clients, so its Rust-flavoured entry would also appear in
the Python changelog.
- Changes only in `objectstore-types` still don't show up in the Rust
changelog, as before, because Craft only collects commits under the
client's directory.
- The two previews share one commit status context ("Changelog Preview /
Semver Impact"), so on a PR touching both clients that status shows
whichever ran last. Each job summary is correct.
- GitHub has a single "Latest" release per repo, so the badge moves
between the two clients.

#skip-changelog

---------

Co-authored-by: sentry-junior[bot] <264270552+sentry-junior[bot]@users.noreply.github.com>
Co-authored-by: Lorenzo Cian <17258265+lcian@users.noreply.github.com>

Author: sentry-junior[bot]

.github/workflows/build-clients.yml .github/workflows/build-python-client.yml.github/workflows/build-clients.yml renamed to .github/workflows/build-python-client.yml

@@ -3,7 +3,7 @@ name: Build Python client
 on:
   push:
     branches:
-      - release-library/**
+      - release-py/**
 
 permissions:
   contents: read

.github/workflows/changelog-preview-python.yml

@@ -0,0 +1,21 @@
+name: Changelog Preview (Python client)
+
+on:
+  pull_request_target:
+    types: [opened, synchronize, reopened, edited, labeled, unlabeled]
+    paths:
+      - clients/python/**
+
+permissions:
+  contents: read
+  pull-requests: write
+  statuses: write
+
+jobs:
+  changelog-preview:
+    uses: getsentry/craft/.github/workflows/changelog-preview.yml@924b450ede4af30e30de4821a4b357d676c8df92 # v3
+    with:
+      working-directory: clients/python
+      # Report as a check with a job summary. In comment mode, both client
+      # previews would overwrite the same PR comment.
+      comment: false

.github/workflows/changelog-preview.yml …hub/workflows/changelog-preview-rust.yml.github/workflows/changelog-preview.yml renamed to .github/workflows/changelog-preview-rust.yml .github/workflows/changelog-preview.yml renamed to .github/workflows/changelog-preview-rust.yml

@@ -1,10 +1,10 @@
-name: Changelog Preview
+name: Changelog Preview (Rust client)
 
 on:
   pull_request_target:
     types: [opened, synchronize, reopened, edited, labeled, unlabeled]
     paths:
-      - clients/**
+      - clients/rust/**
 
 permissions:
   contents: read
@@ -15,4 +15,7 @@ jobs:
   changelog-preview:
     uses: getsentry/craft/.github/workflows/changelog-preview.yml@924b450ede4af30e30de4821a4b357d676c8df92 # v3
     with:
-      working-directory: clients
+      working-directory: clients/rust
+      # Report as a check with a job summary. In comment mode, both client
+      # previews would overwrite the same PR comment.
+      comment: false

.github/workflows/ci.yml

@@ -5,7 +5,8 @@ on:
     branches:
       - main
       - release/**
-      - release-library/**
+      - release-py/**
+      - release-rust/**
 
   pull_request:
 
@@ -244,7 +245,7 @@ jobs:
         if: github.ref == 'refs/heads/main'
 
   validate_gocd:
-    if: ${{ !startsWith(github.ref, 'refs/heads/release/') && !startsWith(github.ref, 'refs/heads/release-library/') }}
+    if: ${{ !startsWith(github.ref, 'refs/heads/release/') && !startsWith(github.ref, 'refs/heads/release-py/') && !startsWith(github.ref, 'refs/heads/release-rust/') }}
     name: Validate GoCD Pipelines
     runs-on: ubuntu-latest
 

.github/workflows/release-clients.yml

@@ -1,8 +1,15 @@
-name: Release client libraries
+name: Release client library
 
 on:
   workflow_dispatch:
     inputs:
+      client:
+        description: Client to release
+        required: true
+        type: choice
+        options:
+          - python
+          - rust
       version:
         description: Version to release
         required: true
@@ -41,4 +48,4 @@ jobs:
           version: ${{ github.event.inputs.version }}
           force: ${{ github.event.inputs.force }}
           merge_target: ${{ github.event.inputs.merge_target }}
-          path: clients
+          path: clients/${{ github.event.inputs.client }}

AGENTS.md

@@ -73,8 +73,7 @@ cargo doc --workspace --all-features --no-deps --document-private-items
 
 ## Pull Requests
 
-When making a change that touches one of the clients, consider the user-facing changelog entry, which is generated from PR titles:
+The Python and Rust clients are released separately, each with its own changelog (`clients/python/CHANGELOG.md`, `clients/rust/CHANGELOG.md`). When making a change that touches one of the clients, consider the user-facing changelog entry, which is generated from PR titles:
 
-- Scope client changes as `py-client` or `rs-client`, e.g. `feat(py-client): Add X`. This allows the automatic changelog generation workflow to pick those changes up.
-- Split changes to both clients into one PR per client.
-- If the title doesn't describe the change well for client users, add a `### Changelog Entry` section to the PR description with the text to use instead.
+- A PR is listed in the changelog of every client whose directory it changes, grouped by the conventional commit type of its title (`feat`, `fix`, ...). The scope doesn't matter.
+- If the title doesn't describe the change well for client users, add a `### Changelog Entry` section to the PR description with the text to use instead. It's used for every client the PR touches.