> 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.1.0.md).

# Release 2.1.0

Release 2.1.0 was published to the Chrome Web Store on August 26, 2024

### Action Required by August 26th: changes to PixieBrix Mod Development

In this release, all mods you’ve built will require a mod id. To simplify the transition, we’ll be automatically updating the mods on your account to have an assigned id.

Here’s what you need to know:

* When 2.1.0 is published on August 26th, we’ll automatically assign an id to each of your saved mods that do not already have an id
* **You will lose access to your id-less mods on August 26th if you do not have a username/alias set for your account**.&#x20;
  * To set a username/alias, open the Page Editor and save any mod
* If you want to manually set a mod id for any mods, save/share the mod before August 26th:
  * On the Extension Console Mods Screen, select “Share with Teams” from the 3-dot menu, and enter a mod id
  * In the Page Editor, save the mod and enter a mod id
* Before upgrading your browser extension to 2.1.0, after August 26th you will see duplicate entries in the Mod Screen for activated mods that don’t have an assigned mod id

Have questions/concerns? Email <support@pixiebrix.com> or visit the [Slack Community](http://slack.pixiebrix.com).

### 🎨 User Experience

* Automatically convert all remaining standalone mod components installed on the Extension to mods (#[8989](https://github.com/pixiebrix/pixiebrix-extension/pull/8989))

### 🐛 Bug Fixes

* Fixed a bug in the Page Editor where the mod version always showed the latest version instead of the activated version (#[9026](https://github.com/pixiebrix/pixiebrix-extension/pull/9026))
* Fixed the integration validation in the Extension Console when activating a mod -- failing to select a required integration will trigger an error message when clicking "Activate" (#[9036](https://github.com/pixiebrix/pixiebrix-extension/pull/9036))


---

# 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.1.0.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.
