v0.9.1 — new hosted endpoint, 2x resources, tested autoscaling

Finishes the migration of the hosted MCP endpoint to a new Azure subscription, right-sizes it, and proves it scales.

🔗 New hosted endpoint

https://patch-tuesday-mcp.agreeabledesert-d0b8e491.eastus2.azurecontainerapps.io/mcp

The old endpoint keeps working until August 11, 2026 (next Patch Tuesday), then retires. Nothing breaks today — but update the URL in your MCP client config before then. The old endpoint now announces its own deprecation via standard Deprecation / Sunset / Link headers (RFC 9745 / 8594 / 5829), a deprecation block in tool responses, and /health.

Local installs are unaffected. uvx patch-tuesday-mcp talks to no hosted endpoint at all.

More resources, real autoscaling

The hosted deployment went from 0.25 vCPU / 0.5 GiB with no scale rule to:

• 0.5 vCPU / 1 GiB per replica
• min 2 / max 6 replicas — no scale-to-zero, no cold starts, and zero-downtime revision rolls
• an http-concurrency autoscale rule with 5x headroom over the trigger

Scaling is now tested, not assumed

New opt-in tests/test_scale.py (never runs in CI) asserts the replica floor and ceiling, CPU/memory, ingress and revision health, and drives dozens of concurrent MCP sessions in ramped waves to confirm real scale-out and a scale-in floor.

It earned its keep immediately, catching two genuine misconfigurations: an autoscale trigger sitting above the server's own connection limit (so replicas would start refusing requests before the platform ever added one), and headroom too thin for the autoscaler's ~60s reaction time.

Notes

• No changes to the default response shape — the deprecation block only appears on a deployment explicitly configured with MCP_DEPRECATION_SUNSET + MCP_DEPRECATION_REPLACEMENT_URL.
• Self-hosters can use the same mechanism to retire their own endpoints; see the README.
• All deprecation text is declarative fact, never instructions aimed at a model — enforced by a test.

Full changelog: v0.9.0...v0.9.1