> For the complete documentation index, see [llms.txt](https://docs.xyo.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xyo.network/documentation-operations/deprecation-and-migration.md). # Deprecation and Migration Policy How XYO documentation marks deprecated libraries and guides readers to supported replacements. ## When a library is deprecated 1. Remove it from new tutorials and cookbook recipes. 2. Add a warning to any page that must remain for existing users. 3. Name the supported public npm replacement. 4. Explain the smallest safe migration path. 5. State the last verified version and verification date. 6. Remove the deprecated page after the announced support window. ## Public-surface rule Documentation may describe a package only when it is publicly downloadable from npm and the referenced symbol is part of its published `exports` map. A public package does not make its source repository public; do not link to source unless repository visibility has been independently verified. CLI packages, private repositories, internal services, unpublished APIs, deep imports outside the `exports` map, and private application behavior are excluded from developer documentation. ## Migration-page template Every migration page should answer: * What changed? * Who is affected? * Which public package and version replaces the old surface? * What code or configuration must change? * How can the reader verify the migration? * When does support for the old surface end? --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.xyo.network/documentation-operations/deprecation-and-migration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.