PiClaw v2.7.2 — "North by Northwest"
A focused Azure OpenAI routing patch: base URLs now get normalised before they wander off into provider country, and the documentation no longer leaves endpoint configuration as an orienteering exercise with cloud billing attached.
Fixes
- Azure OpenAI base URLs are now normalised before use, so deployment endpoints are less likely to fail because one slash, path fragment, or over-helpful configuration field decided to become infrastructure.
- Provider definitions and Azure OpenAI routing now agree on the expected endpoint shape, because “same setting, different interpretation” is not a feature, it is a debugging subscription.
- Azure OpenAI extension documentation was updated around endpoint configuration, making the setup path less dependent on folklore and copy-pasted portal archaeology.
Under the hood
- Added routing coverage for Azure OpenAI URL normalisation, because cloud endpoint handling without tests is just optimism wearing a lanyard.
- Touched the provider definition and Azure integration path only; this is intentionally narrow, which is rare enough to mention in public.
Known issues
- Azure OpenAI still has Azure-shaped configuration complexity; this release normalises URLs, it does not make the portal develop taste.
- Existing bad configuration may still need to be corrected once, but at least the runtime is now less eager to preserve the mistake verbatim.
Upgrade
- Upgrade normally; no database migration is required.
- If Azure OpenAI endpoint setup stops feeling like a compass test in low visibility, that is intentional.