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

# Release 1.8.2

Release 1.8.2 was released to the Chrome Web Store on November 6, 2023

### ✨ Enhancements

* Custom trigger event names now show up in the “Emit Custom Event” dropdown when created in the trigger starter brick (#[6519](https://github.com/pixiebrix/pixiebrix-extension/pull/6698))

### 🐛 Bug Fixes

* Fixes issue where changing the Control Room URL when logging into an AA Control Room didn’t update the URL (#[6653](https://github.com/pixiebrix/pixiebrix-extension/pull/6654))
* Fixes UI bug where the select button for the legacy Google Sheets picker in the Page Editor obscured part of the dropdown menu for the Google Drive integration picker (#[6736](https://github.com/pixiebrix/pixiebrix-extension/pull/6737))
* The Google Sheet dropdown now includes Google Sheets from shared drives that the user has accessed (#[6701](https://github.com/pixiebrix/pixiebrix-extension/pull/6770))
* The Google Drive integration no longer launches multiple web auth flows (#[6684](https://github.com/pixiebrix/pixiebrix-extension/pull/6781))
* Better error handling in the Page Editor when the user does not have access to the Google Drive resource. The user can now try again or select a different sheet (#[6779](https://github.com/pixiebrix/pixiebrix-extension/pull/6787))

### 🎨 User Experience

* When creating a new Google Drive integration (`google/oauth2-pkce`), the authorization flow is now triggered automatically and the label is generated from the email account used (#[6269](https://github.com/pixiebrix/pixiebrix-extension/pull/6734))
* Various performance improvements (#[6786](https://github.com/pixiebrix/pixiebrix-extension/pull/6788), #[4000](https://github.com/pixiebrix/pixiebrix-extension/pull/6780), #[6784](https://github.com/pixiebrix/pixiebrix-extension/pull/6785), #[6776](https://github.com/pixiebrix/pixiebrix-extension/pull/6776), #[6777](https://github.com/pixiebrix/pixiebrix-extension/pull/6777), #[6690](https://github.com/pixiebrix/pixiebrix-extension/pull/6775), #[6581](https://github.com/pixiebrix/pixiebrix-extension/pull/6772), #[6690](https://github.com/pixiebrix/pixiebrix-extension/pull/6774), #[6804](https://github.com/pixiebrix/pixiebrix-extension/pull/6806))


---

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