> For the complete documentation index, see [llms.txt](https://docs.blockbrain.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.blockbrain.ai/for-admins/web-components/web-component-versioning-overview-and-guide.md).

# Web Component Versioning – Overview & Guide

#### 1. Current Setup (Legacy URL)

You are currently using the following build URL:

🔗 <https://assets.theblockbrain.ai/scripts/blocky-chat/blocky-chat.bundle.js>

This is the legacy URL and will always serve the latest version automatically. No action is needed if you want to stay on the most recent version using this URL.

***

#### 2. New Versioning URLs

With the new versioning feature, you now have two options to control which version of the web component you use:

| Option         | URL                                                                                    | Description                                                                                                                 |
| -------------- | -------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------- |
| Always Latest  | <https://assets.theblockbrain.io/scripts/blocky-chat/latest/blocky-chat.bundle.js>     | Automatically points to the newest version at all times.                                                                    |
| Pinned Version | <https://assets.theblockbrain.io/scripts/blocky-chat/v1.0.1-rc5/blocky-chat.bundle.js> | Points to a specific version (e.g., `v1.0.1-rc5`). Replace the version segment in the URL to switch to a different version. |

All available versions and release tags are managed and published here:\
🔗 <https://github.com/theblockbrain/b2b-webcomponents/releases>\
\
Language

The web component ships its built-in UI texts - button labels, the "New Conversation" title, and the "Write your message" input placeholder - in **English (default)** and **German**. The language is selected by the bundle path: add the locale segment **after** the version segment.

| Language           | Locale segment | Example URL                                                                           |
| ------------------ | -------------- | ------------------------------------------------------------------------------------- |
| English (default)  | *(none)*       | `https://assets.theblockbrain.io/scripts/blocky-chat/latest/blocky-chat.bundle.js`    |
| English (explicit) | `/en/`         | `https://assets.theblockbrain.io/scripts/blocky-chat/latest/en/blocky-chat.bundle.js` |
| German             | `/de/`         | `https://assets.theblockbrain.io/scripts/blocky-chat/latest/de/blocky-chat.bundle.js` |

The pattern works with any version: `.../scripts/blocky-chat/{version}/{locale}/blocky-chat.bundle.js` (e.g. `latest/de/` or `v1.0.5/de/`).

To switch the widget to German, change only the script `src` — keep all other attributes (`orgId`, `uid`, `userUid`, `publicToken`) unchanged:

​​

```
<script
  async defer
  src="https://assets.theblockbrain.io/scripts/blocky-chat/latest/de/blocky-chat.bundle.js"
  orgId="..." uid="..." userUid="..." publicToken="...">
</script>
```

> **Note:** This path controls only the component's built-in static texts. The welcome message and the bot's answers follow the platform's language settings and are not affected by this path. If the static labels appear in English on a German site, the embed is loading the default (English) bundle — switch the `src` to the `/de/` path.

Only English and German are available today.

***

#### 3. How to Switch Versions

Switching to a different version is straightforward:

1. Choose the [desired version](https://github.com/theblockbrain/b2b-webcomponents/releases)
2. Replace the version segment in the URL (e.g., change `v1.0.1-rc5` to the new version tag).
3. Update the script reference in your integration to use the new URL.

That's it — no further configuration is required.

***

#### 4. How Will You Know About New Versions?

* If you use the `/latest/` URL, you will always receive the newest version automatically.
* If you use a pinned version URL, we will notify you whenever a new version is released (including new features and release tags).

***

#### 5. Web Component Configuration

You can manage your web component settings directly in your admin tab. Each tenant has a dedicated Web Components tab for managing their specific configuration:

🔗 <https://into.theblockbrain.ai/manage?tab=webcomponents>


---

# 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.blockbrain.ai/for-admins/web-components/web-component-versioning-overview-and-guide.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.