> ## Documentation Index
> Fetch the complete documentation index at: https://veriqa.app/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# 0.6.5 — Messenger, WeChat and Viber (upcoming)

> What Veriqa 0.6.5 brings: the Messenger, WeChat and Viber channels, a dark theme for service pages, hop mode per application, superseding unfinished sign-ins.

<Note>
  This version is being prepared for release: nothing described here is in the published packages
  and image yet. The latest release is [0.6.1](/docs/releases/0.6#061).
</Note>

## Three new channels

[Messenger](/docs/guides/channels#messenger), [WeChat](/docs/guides/channels#wechat) and
[Viber](/docs/guides/channels#viber) become built-in channels of the core. Viber was tested against a
Bot API stand-in, with no live run. A refusal from the Messenger, Instagram and Viber clients
now comes back as a result instead of an exception, and a repeated "Yes" or "No" no longer sends a
new message.

## The sign-in page and hop mode

* Service pages follow the `Theme` setting, the dark theme included.
* Hop mode can be turned on for one application or tenant — see
  [Hop mode for one application](/docs/reference/configuration#hop-mode-for-one-application).
* Sign-in errors are returned to the client with a redirect.

## Sign-ins and transactions

* **A new sign-in supersedes the same user's unfinished ones** — see
  [A new sign-in closes the earlier ones](/docs/guides/storage#a-new-sign-in-closes-the-earlier-ones).
* **A sign-in survives the issuing of the authorization code:** for a sign-in already redeemed, the callback
  answers that the session has expired.
* **Two linked bots** — the `{handle}` slot; see [Two bots](/docs/guides/existing-bot#two-bots).
* The HTTP channel passes the phone number, on request or automatically.

## What to check when you upgrade

* **A new EF Core migration** for the transaction store — apply it when you upgrade.
* **Parallel sign-ins of one user:** an unfinished sign-in closes as soon as the same user starts a
  new one. If your scenario keeps two sign-ins open at once, check it.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.