> ## 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.4 — Instagram, sign-in page texts and PathBase (upcoming)

> What Veriqa 0.6.4 brings: the Instagram channel, markup in sign-in page texts, a host under a path prefix, the Menu and Redirect post-actions.

<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>

## Instagram

Instagram Direct is a built-in channel of the core: the user signs in through a conversation with your
Instagram account — see [Instagram](/docs/guides/channels#instagram).

## The sign-in page

* **Inline markup in `Title`, `Instruction` and a channel hint** — see
  [Markup in the title, the instruction and a channel hint](/docs/guides/customization#markup-in-the-title-the-instruction-and-a-channel-hint).
* The built-in instruction names only what the page shows, and a single-channel page names its
  channel. A new page for an expired sign-in.
* The claim completion state is visible in the channel; the Telegram phone keyboard is removed after
  the answer; "Cancel sign-in" sits under the completion form.

## Channels

The `Menu` and `Redirect` post-actions for Telegram and MAX — what the bot shows after the sign-in;
see [Veriqa:CompletionBehavior](/docs/reference/configuration#veriqacompletionbehavior).

## Operations

A host under a base path prefix — `Veriqa:PathBase`; see
[Under a path prefix](/docs/guides/reverse-proxy#under-a-path-prefix).

## What to check when you upgrade: sign-in page wording

Your own wording set for one of the built-in texts below — in `AuthPage:Texts` or in a locale file —
stops applying where the page no longer shows that text. Move it to the new key:

| Where | Key that stops applying there | Key to move the wording to |
| - | - | - |
| Expired sign-in | `Session expired` | `This sign-in request has expired` |
| Single-channel page — whatever it shows | `Scan the QR code or tap the channel button` · `Tap the channel button to sign in` | `Scan the QR code or tap the button to sign in via {0}` · `Scan the QR code to sign in via {0}` · `Tap the button to sign in via {0}` |
| Several channels with their own QR codes, buttons hidden | `Choose a channel and scan the QR code or tap the button` | `Choose a channel and scan the QR code` |
| Several channels behind one QR code, buttons hidden | `Scan the QR code or tap the channel button` | `Scan the QR code to sign in` |

The earlier keys stay in force only on a multi-channel page that shows a button. A replacement for a
single-channel text must carry the `{0}` slot, where the page puts the channel's icon and name.
Delete the earlier docs recipe for a screen with hidden buttons — the `tv-app` example: the
instruction now follows the button by itself. The full table of variants is in
[The instruction follows both settings](/docs/guides/customization#the-instruction-follows-both-settings).

**`Title`, `Instruction` and a channel hint already set as plain text may look different:** these
texts are now read as HTML. `Terms &amp; Conditions` now shows "Terms & Conditions", and a bare `<`
or `>` fails the check — the value is shown as written and a warning goes to the log. Review your
values for `&`, `<` and `>`.


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