> For the complete documentation index, see [llms.txt](https://docs.bindplane.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bindplane.com/changelog/january-2024/2024-01-31-release.md). # 2024-01-31-Release Version 1.42.0 • JAN 31, 2024 ## New Features * Azure Event Hub Source ## Bug Fixes and Improvements * Improved OpAMP debugging ## Migration Notes This release includes a change that will **break future downgrade compatibility** for users with a single account boltstore installation of BindPlane. Before upgrading, those users should [create a backup](https://github.com/observIQ/bindplane-docs/blob/main/configuration/bindplane/backup-and-disaster-recovery/bolt-store.md) of their storage file, which can be used in the event of a downgrade.\* To downgrade, those users should follow these steps: 1. Stop the BindPlane service 2. Replace the storage file with the backed-up version 3. Restart the BindPlane service Changes made after upgrading will not be persisted when performing this downgrade.\\ \* If, instead, BindPlane is configured with either multi-account or postgres, this release is backward compatible and no action is needed to downgrade safely. BindPlane is multi-account if `accounts.enable` is `true` in its configuration: ```yaml accounts: enable: true ``` --- # 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.bindplane.com/changelog/january-2024/2024-01-31-release.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.