> For the complete documentation index, see [llms.txt](https://docs.ergonode.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ergonode.com/ergonode-transfer/changelog/breaking-changes.md). # Breaking changes At Ergonode we strive to make your integration process as fluent as possible but from time to time we discover a flaw in the design of the schema or introduce a really cool new feature that is impossible to be provided in a fully-compatible non-breaking way. In such a situation, we will always aim to not break your integration with the new release and provide you with a transition period of approximately 3-months to adjust your consumer. Every such change shall be communicated in the following list. ## 2024-05-14 Breaking change scheduled for 09-2024 * templates\_elements.csv `label` is going to be removed * section\_templates\_elements.csv `label` is going to be removed ## 2022-10-11 Breaking change scheduled for 01-2023 * options.csv `_label` is going to be removed ## 2022-06-09 Breaking change scheduled for 10-2022 * templates.csv `_name` is going to be removed ## 2022-05-10 Breaking change scheduled for 07-2022 * templates.csv `_language` is going to be removed ## 2022-03-15 Breaking change scheduled for 07-2022 * attributes.csv `_placeholder` is going to be removed --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ergonode.com/ergonode-transfer/changelog/breaking-changes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.