> For the complete documentation index, see [llms.txt](https://developer.thunderbird.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.thunderbird.net/add-ons/updating/updates-for-thunderbird-140.md).

# Updates for Thunderbird 140

{% hint style="warning" %}
Individual change lists are no longer published for each release.
{% endhint %}

Modern WebExtensions are generally stable and do not require ongoing updates to remain compatible. For Experiment add-ons, the number of potential changes in Thunderbird’s core code has grown so large that tracking and documenting every incompatibility is not an effective use of resources.

It has proven more effective to discuss compatibility issues during the [**weekly add-on developer call** or on the **add-on developer mailing list**](/add-ons/community.md). These forums allow developers to raise questions, share experiences, and collaborate on solutions with the community.


---

# 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://developer.thunderbird.net/add-ons/updating/updates-for-thunderbird-140.md?ask=<question>&goal=<endgoal>
```

`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.