Skip to content

Changelog for v0.17.3 #1429

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
phinze merged 1 commit into from
Nov 4, 2026
Merged

Changelog for v0.17.3 #1429

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions docs/docs/changelog.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,6 +22,17 @@ All notable changes to Miren Runtime will be documented in this file.

---

## v0.17.3
*2026-11-04*

**Bug Fixes**
- **Busy autoscaled services keep serving at capacity instead of hanging** - When every sandbox hit its `requests_per_instance` target, requests parked in the activator waiting for a new sandbox, and failed with "no sandbox became available within 120 seconds" even when the sandboxes had room. Once a service reached its maximum of 20 instances, no new sandbox could come, so requests hung until they timed out. Requests now go to the least-loaded sandbox and the pool grows in the background. At the maximum, requests keep spreading across the sandboxes a service has. A response cut off partway, by a client hanging up or a silent stream timing out, also no longer leaks capacity for the life of the sandbox, and a scale-down can no longer overwrite a scale-up that happened at the same moment. ([#1387](https://github.com/mirendev/runtime/pull/1387))
- **Metrics forwarding refuses certificates from the compromised eMudhra intermediates** - vmagent was the last component Miren ships that still verified public certificates on a Go release without the distrust. It sends metrics with a bearer token, so a certificate chained through those intermediates could have captured that token. Miren now ships vmagent v1.155.0, built on Go 1.27.3, with no change to how vmagent behaves. ([#1425](https://github.com/mirendev/runtime/pull/1425))
- **Servers clean up leftover containerd daemons** - If Miren exited without running its stop hooks, after a panic for example, its containerd kept running. Every containerd started after that hung waiting for the lock while the old one kept answering, so a host could quietly run a months-old containerd and collect a stuck daemon for each restart. Miren now stops leftovers before starting its own, and a second server on the same data directory refuses to start. Sandboxes keep running throughout. The first restart on this release cleans up a host that's already in this state. ([#1416](https://github.com/mirendev/runtime/pull/1416))
- **Servers stop promptly instead of stalling on dead connections** - Every upgrade sat idle for about 16 seconds after SIGTERM with public ingress already down, waiting on connections whose peers had gone away. Shutdown now waits only for handlers that are still running, and `miren` CLI commands close their connections when they exit. ([#1408](https://github.com/mirendev/runtime/pull/1408))

---

## v0.17.2
*2026-10-21*

Expand Down
Loading