> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/release-notes/release-notes-archive/release-2.0.5.md).

# Release 2.0.5

{% hint style="info" %}
As of 2.0.5, Standalone Mod Components are now deprecated. Over the next upcoming releases, we will be migrating to a model where all mod components will always be within a packaged mod
{% endhint %}

### 🎨 User Experience

* When saving a standalone mod component, developers will now see the `Save new mod` modal (#[8745](https://github.com/pixiebrix/pixiebrix-extension/pull/8745), #[8795](https://github.com/pixiebrix/pixiebrix-extension/pull/8795), #[8796](https://github.com/pixiebrix/pixiebrix-extension/pull/8796))
* Updated the Data Panel in the Page Editor to always show mod variables (#[8760](https://github.com/pixiebrix/pixiebrix-extension/pull/8760))
* Deployed mods are now activated on existing tabs on initial activation (#[8755](https://github.com/pixiebrix/pixiebrix-extension/pull/8755))
* Removed the browser warning on the Extension Console when installing the Extension on Microsoft Edge (#[8802](https://github.com/pixiebrix/pixiebrix-extension/pull/8802))

### 🐛 Bug Fixes

* Fixed bug where nunjucks expressions would fail to run, leading to a \`RENDER\_NUNJUCKS not available within 3 seconds\` message appearing to users (#[8792](https://github.com/pixiebrix/pixiebrix-extension/pull/8792)) 
* Fixed bug where adding a new Google Auth Integration during mod activation in the Extension Console failed to refresh the available spreadsheets from the picker (#[8803](https://github.com/pixiebrix/pixiebrix-extension/pull/8803))


---

# 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.pixiebrix.com/release-notes/release-notes-archive/release-2.0.5.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.