# MGS v1.1.1 ### New Features & Enhancements #### Nested URL Paths in Policy Aliases Policy authors can now use nested, slash-separated paths when defining policy aliases (for example, `dmrv/farm/measurements`). Previously, aliases were restricted to a single flat segment, which made it harder to organize multiple DMRV endpoints under a clean, hierarchical URL structure. * The alias validator and Swagger documentation now accept nested paths. * Existing single-segment aliases continue to work exactly as before. * The change is reflected in both the policy configuration UI and the generated API documentation. #### A Cleaner Policy API Self-Documentation Response The policy `/about` endpoint, which describes the public API surface of a published policy, has been tidied up so its output is easier to consume by downstream tools and integrations. * Schema identifiers are now returned without the leading `#` character, matching how they are referenced everywhere else in the platform. * Block documentation URLs are now consistently constructed with a `/blocks` segment, so callers no longer need to special-case different URL shapes. #### Quick Feedback When Copying from the API Documentation Dialog The API Documentation dialog, which policy authors use to inspect and share the public surface of a policy, now shows a brief confirmation toast whenever a URL or identifier is copied to the clipboard. This removes the small uncertainty about whether the copy action took effect. ### Platform Stability #### DMRV GET Endpoint Routing Fix A GET request to a DMRV endpoint without query parameters now correctly matches the `/tag/:tag/blocks` URL advertised in the policy's own API documentation. Previously, the request would fall through to a different handler in certain cases, returning an unexpected response shape. Integrations that rely on the published DMRV URLs will now behave consistently with what the documentation describes. *** For the full changelog and release notes on the open-source Guardian please visit: --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.guardianservice.app/whats-new/release-notes/mgs-v1.1.1.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.