# Migration guides

It is hard to build a framework or big library that preserves the backward compatibility in every aspect from the very first iterations. We are still learning from release to release and want to deliver the best developer experience as possible without breaking changes, but as you know, it is not so simple. Sometimes you just find a better way of approaching the problem. Your point of view/perspective shifts as you mature as a developer — striving for perfection.

{% content-ref url="/pages/-MlUJoEV3I6OUio75Yy8" %}
[Migration from version 3.x](/docs/other/migration-guides/version-3.md)
{% endcontent-ref %}

{% content-ref url="/pages/-M-RdyMDrSCSoT\_Y4v8f" %}
[Migration from version 2.x](/docs/other/migration-guides/version-2.md)
{% endcontent-ref %}

{% content-ref url="/pages/-LXydGnyzBdwrEXMzDzm" %}
[Migration from version 1.x](/docs/other/migration-guides/version-1.md)
{% endcontent-ref %}


---

# 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://marblejs.gitbook.io/docs/other/migration-guides.md?ask=<question>
```

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.