> For the complete documentation index, see [llms.txt](https://docs.welkinhealth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.welkinhealth.com/release-notes/readme.md). # Welkin Health — Release Notes Welkin Health release notes and product changelog with new features, platform updates, enhancements, and workflow improvements across each bi-weekly release. All product updates, new features, and improvements to the Welkin Health platform. *** Welkin Health publishes release notes on a bi-weekly cadence. Each version uses year-and-sprint numbering, such as `2026.YX.Z`. Browse the yearly changelog archives below. ## 2026 * [2026 Changelog](/release-notes/changelog.md) — Versions 2026.65.0 through 2026.78.0 ## 2025 * [2025 Changelog](/release-notes/changelog-2025.md) — Versions 2025.59.0 through 2025.68.0 ## 2024 * [2024 Changelog](/release-notes/changelog-2024.md) — Versions 2024.42.0 through 2024.58.0 --- # 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.welkinhealth.com/release-notes/readme.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.