chore(main): release slim-testutils 0.7.2

[build-agntcy]

🤖 I have created a release beep boop

0.7.2 (2026-08-04)

Features

• add header integrity check and replay protection to control messages (#1740) (07440be)
• add spire support to test apps (#1939) (8e7d8d4)
• add websocket supports for the browser (#1775) (2dbdb0c)
• bindings: expose session close/rejoin (#1896) (c8fa51f)
• session: encrypted MLS + session state persistence and restore (#1820) (bf06ac1)

Bug Fixes

• update SPIRE version to 1.15.2 (#1904) (8333f2c)

---

This PR was generated with Release Please. See documentation.

[github-actions]

The latest Buf updates on your PR. Results from workflow ci-buf / buf (pull_request).

Build	Format	Lint	Breaking	Updated (UTC)
✅ passed	✅ passed	✅ passed	✅ passed	Jun 9, 2026, 4:48 AM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[coderabbitai]

Warning

Review limit reached

@build-agntcy, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: f6858a9f-b16f-4142-8b25-03f144ae7ed2

📥 Commits

Reviewing files that changed from the base of the PR and between 37dfab3 and 73d1114.

📒 Files selected for processing (2)

• .github/release-manifest.json
• crates/testing/CHANGELOG.md

📝 Walkthrough

Walkthrough

The release manifest sets crates/testing to version 0.7.2. The changelog adds the 0.7.2 release entry dated 2026-08-04 and lists its changes.

Changes

Testing crate release

Layer / File(s)	Summary
Update release metadata and changelog .github/release-manifest.json, crates/testing/CHANGELOG.md	The manifest changes the crates/testing version from 0.7.1 to 0.7.2. The changelog adds the 0.7.2 release entry and lists its feature and bug-fix changes.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: msardara

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The title clearly identifies the release of slim-testutils version 0.7.2.
Description check	✅ Passed	The description documents the 0.7.2 release, lists changes, links related issues and commits, and identifies Release Please as the generator.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-please--branches--main--components--slim-testutils

---

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@crates/testing/CHANGELOG.md`:
- Line 10: Update the changelog entry wording from “add websocket supports for
the browser” to “add WebSocket support for browsers,” preserving the existing
issue and commit links.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: ffc5ca8c-dd1b-4e88-b1b3-ca3944d55ca6

📥 Commits

Reviewing files that changed from the base of the PR and between 8e7d8d4 and 7f51180.

📒 Files selected for processing (2)

• .github/release-manifest.json
• crates/testing/CHANGELOG.md

[coderabbitai]

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Correct the WebSocket changelog wording.

Change add websocket supports for the browser to add WebSocket support for browsers.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@crates/testing/CHANGELOG.md` at line 10, Update the changelog entry wording
from “add websocket supports for the browser” to “add WebSocket support for
browsers,” preserving the existing issue and commit links.