chore(main): release 8.61.1

[pjb157]

🤖 I have created a release beep boop

8.61.1 (2026-06-19)

Bug Fixes

• deps: bump fusillade to 19.0.0 (#1162) (e041b40)
• playground: render reasoning from all backend fields (#1158) (e1ee0a6)

---

This PR was generated with Release Please. See documentation.

[cloudflare-workers-and-pages]

Deploying control-layer with    Cloudflare Pages

Latest commit:	f9b7db3
Status:	✅  Deploy successful!
Preview URL:	https://c6c55d97.control-layer.pages.dev
Branch Preview URL:	https://release-please--branches--ma.control-layer.pages.dev

View logs

[Copilot]

Pull request overview

Prepares the dwctl backend for the 8.61.1 release by updating version metadata and release artifacts to reflect the previously-merged dependency fix (fusillade 19.0.0).

Changes:

• Bump dwctl crate version to 8.61.1.
• Update release-please manifest and both lockfiles to align with the release version.
• Prepend the 8.61.1 entry to CHANGELOG.md.

Reviewed changes

Copilot reviewed 3 out of 5 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
dwctl/Cargo.toml	Bumps the crate version to 8.61.1.
dwctl/Cargo.lock	Updates the dwctl package entry to 8.61.1 in the dwctl lockfile.
Cargo.lock	Updates the dwctl package entry to 8.61.1 in the workspace lockfile.
CHANGELOG.md	Adds the 8.61.1 release notes section.
.release-please-manifest.json	Updates release-please manifest to 8.61.1.

[doubleword-code]

Summary

This is a release PR that bumps the version from 8.61.0 to 8.61.1 and updates the CHANGELOG to document the fusillade dependency upgrade. The actual dependency changes (fusillade 18.0.2 → 19.0.0, onwards 0.32.0 → 0.33.1) were already merged in commit e041b40.

Verdict: Ready to merge — this is a standard release-please generated release commit with no code changes to review.

Research notes

• Fusillade 19.0.0 is a breaking release that fixes a race condition where retry could resurrect requests under finalized batches (fusillade#295)
• The upgrade includes a fusillade schema migration that runs automatically on dwctl startup
• onwards was upgraded from 0.32.0 to 0.33.1 to maintain compatibility (0.33.1 widened its fusillade range to >=17.0.2, <20)

Suggested next steps

1. Deploy with awareness of schema migration: The fusillade 18→19 upgrade includes a schema migration. While this runs automatically on startup, ensure your deployment strategy accounts for this during rollout.

2. Monitor batch processing after deploy: Given this release fixes a finalize-then-resurrect race condition in batch retry logic, monitor batch completion metrics for any behavioral changes.

General findings

No issues found. The PR correctly:

• Updates .release-please-manifest.json to reflect the new version
• Adds an accurate CHANGELOG entry linking to PR #1162
• Updates both Cargo.lock files and dwctl/Cargo.toml version consistently

[doubleword-code]

Summary

This is a release-please generated PR bumping the version from 8.61.0 to 8.61.1. It releases two upstream fixes:

1. fusillade dependency bump (18.0.2 → 19.0.0) - A breaking change that fixes a race condition where retry could resurrect requests under finalized batches, preventing orphaned pending requests under completed batches. Also includes a fusillade schema migration that runs on dwctl startup.
2. Playground reasoning fix - Fixes rendering of reasoning content from different backend fields (reasoning_content, reasoning, reasoning_details[], and inline `` tags), plus adds a 404 failover toggle to the model routing configuration UI.

Verdict: Approved for release, but note the temporary E2E test disablement should be reverted once Playwright downloads recover.

Research notes

• fusillade#295: Referenced in the dependency bump commit as the issue fixed by version 19.0.0 - prevents retry from resurrecting requests under finalized batches.
• onwards 0.32.0 → 0.33.1: Required to resolve the dependency tree with fusillade 19; version 0.33.1 widened its fusillade range to >=17.0.2, <20.
• The reasoning fix handles multiple backend response formats observed in production: some backends send reasoning_content, others send reasoning + reasoning_details[] (as duplicates in the same chunk), and some models emit thinking inline via `` tags.

Suggested next steps

1. Re-enable E2E tests - Once the upstream Playwright browser-download outage is resolved, revert the .github/workflows/ci.yaml change to restore the e2e-test-docker job condition.
2. Monitor schema migration - The fusillade 18→19 upgrade includes a schema migration that runs on dwctl startup. Verify migration completes successfully on deployment.
3. Test 404 failover - After deployment, verify the new 404 failover toggle works as expected for self-hosted models that return 404 when not live.

General findings

• The reasoning.ts helper is well-designed with comprehensive unit tests (14 cases) covering edge cases like double-counting prevention, budget-exhausted-while-thinking, and mid-stream think tag handling.
• The 404 failover toggle is frontend-only; the backend already supports arbitrary status codes in fallback_on_status, so no backend migration is needed.
• The CI workflow change includes a clear TODO comment explaining the temporary disablement and the condition to restore.

[pjb157]

🤖 Created releases:

• v8.61.1

🌻