This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
+9 more
Affected surfaces
ReleasePort's take
Light signalProfile secret preservation is now guaranteed during profile updates unless a non‑secret auth method replaces it, and Windows TLS startup stability has improved by removing rustls debug assertions.
Why it matters: Ensures saved secrets remain intact on update payloads and eliminates rustls native-root debug assertion failures that previously destabilized Windows TLS initialization; relevant for all deployments using these features.
Summary
AI summaryEditing profile updates now preserve saved secret unless switching to a non‑secret auth method, and Windows TLS startup stability improved by removing rustls debug assertions.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Bugfix | Medium |
Preserves profile secret when omitted in update payload. Preserves profile secret when omitted in update payload. Source: llm_adapter@2026-05-23 Confidence: high |
— |
| Bugfix | Medium |
Removes rustls native-root debug assertion for Windows TLS startup stability. Removes rustls native-root debug assertion for Windows TLS startup stability. Source: llm_adapter@2026-05-23 Confidence: high |
— |
Full changelog
Brows3 0.2.35 release notes
Fixed
- Profile Secret Preservation: Editing a profile between manual credentials and custom S3-compatible endpoints now preserves the saved secret when the update payload omits it, and only clears stored secrets when switching to a non-secret authentication method.
- Windows TLS Startup Stability: Updated the AWS SDK runtime stack to remove the rustls native-root debug assertion path without replacing the operating system trust store.
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About rgcsekaraa/brows3
All releases →Related context
Related tools
Beta — feedback welcome: [email protected]