Skip to main content
A development stage from October 10 to 11, 2026. There is no 0.6.8 package: these changes shipped in 0.7.0.

​
Three new channels

Messenger, WeChat and Viber are now built into the core. Viber was tested against a Bot API stand-in, with no live run. A refusal from the Messenger, Instagram and Viber clients 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.
  • 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.
  • A sign-in survives the issuing of the authorization code: for a sign-in already redeemed, the callback answers that the session has expired.

​
Channels

  • Two linked bots — the {handle} slot; see Two bots.
  • The HTTP channel passes the phone number, on request or automatically.

​
What to check when you upgrade

  • New EF Core migrations for the transaction store.
  • Parallel sign-ins of one user: when a user starts a new sign-in and reaches the channel with the same account, that account’s unfinished sign-ins to the same application close. If your scenario keeps two sign-ins open at once, check it.
The full list is in What to check when you upgrade from 0.6.1.