Release v1.10.0: banner colours + urgent, and 3 UI fixes #183

Merged

developer merged 8 commits from development into master 2026-07-05 14:10:25 +00:00

Conversation 1 Commits 8 Files Changed 38

+1403 -173

developer commented 2026-07-05 14:04:12 +00:00

Owner

Copy Link

Copy Source

Promote development → master for the v1.10.0 production release.

Contents (4 merged PRs)

• #182 feat(banner): per-campaign colour overrides + urgent alerts — carries schema migration 00009 (additive, expand-contract).
• #181 fix(ui): hold info toast ~1s before it rises and fades.
• #180 fix(ui): poll for out-of-band email confirmation.
• #179 feat(ui): hide current-host sign-in row in profile.

All four are green on development and live on the test contour.

Prod deploy notes

• The prod deploy auto-detects migration 00009 → opens a maintenance window ("технические работы" + a consistent pg_dump, backend frozen) on the main host, forward-migrates, health-gated rolling roll of both hosts, auto-rollback to the previous tag on failure.
• Migration is expand-contract → image rollback stays DB-safe.
• Release tagged v1.10.0 on master before dispatch (deploy stamps git describe --tags).

After merge + tag: prod-deploy.yaml (confirm=deploy) → verify prod serves v1.10.0.

Promote `development` → `master` for the **v1.10.0** production release. ## Contents (4 merged PRs) - **#182** feat(banner): per-campaign colour overrides + urgent alerts — **carries schema migration 00009** (additive, expand-contract). - **#181** fix(ui): hold info toast ~1s before it rises and fades. - **#180** fix(ui): poll for out-of-band email confirmation. - **#179** feat(ui): hide current-host sign-in row in profile. All four are green on `development` and live on the test contour. ## Prod deploy notes - The prod deploy auto-detects migration 00009 → opens a **maintenance window** ("технические работы" + a consistent `pg_dump`, backend frozen) on the main host, forward-migrates, health-gated rolling roll of both hosts, **auto-rollback** to the previous tag on failure. - Migration is expand-contract → image rollback stays DB-safe. - Release tagged **v1.10.0** on `master` before dispatch (deploy stamps `git describe --tags`). After merge + tag: `prod-deploy.yaml` (`confirm=deploy`) → verify prod serves v1.10.0.

developer added 8 commits 2026-07-05 14:04:12 +00:00

feat(ui): hide current-host sign-in row in profile ... c1805e5b7c

Inside a Telegram/VK Mini App the host provider is auto-linked. Once the
player also linked an email, `canUnlink` turned true and the "Unlink"
control appeared on the host platform's own row — letting them unlink the
very platform they are signed in through, which is meaningless.

Gate the Telegram row on `!insideTelegram()` and the VK row on
`!insideVK()`, reusing the runtime host detectors that already gate the
"link" buttons. Symmetric: inside TG only the TG row is hidden (the VK row
still shows, since VK is not the current host), and vice versa. The web and
native builds are unchanged (both detectors are false there); the backend
is untouched — this is a UI display gate, and `linkUnlink` still refuses to
remove the last identity.

Docs: FUNCTIONAL.md (+_ru mirror).

fix(ui): poll for out-of-band email confirmation ... fb7490f1df

An email link/code can be confirmed out of band: the recipient taps the
one-tap link in the email, which confirms in another browser/session. The
backend already publishes a `notify` `profile` re-fetch signal for this
(handlers_auth.go handleEmailConfirmLink), and the client re-fetches on it.

But the live stream is single-shot with no replay: a Mini App backgrounded
while the user is in their mail app tapping the link drops the stream and
misses the event (the gateway hub has no subscriber to deliver to), and the
reconnect on foreground does not re-sync — so the open code form stayed
until a manual reload. On Telegram Desktop the app is never backgrounded,
so the push works and there was no bug.

Add a client-side fallback: while an add-email confirmation is pending
(a code was sent, no email yet), poll `profile.get` on a 4s interval and on
foreground regain until the address lands; the effect stops as soon as the
email appears. The live push still updates instantly when foregrounded —
this only covers the backgrounded-miss gap.

Tests: a mock e2e attaches the email WITHOUT emitting a live event (new
window.__mock.clearEmail / confirmEmailOutOfBand seams), so it exercises the
poll, not the push, and asserts the code form collapses into the email row.
Docs: ARCHITECTURE.md §10 notes the single-shot gap + the poll fallback.

fix(ui): hold info toast ~1s before it rises and fades ... 400b6ac2a5

The info toast began drifting up and fading the instant it finished
appearing (the CSS keyframes went straight from the 12% appeared-stop to
the 100% risen-and-faded stop), so a glanced message was already leaving.

Insert a ~1s hold at full opacity/rest before the rise-and-fade: extend the
animation 2s → 3s with keyframe stops at 8% (appeared, ~240ms) and 41% (end
of the ~1s hold), keeping the original rise-and-fade pace for the tail. The
reduced-motion variant gets the same appear/hold/fade timing (fade only, no
travel). The showToast dismissal timer is bumped 2000 → 3000ms to stay in
lockstep with the animation (the error toast's 4s dwell is unchanged).

Merge pull request 'feat(ui): hide current-host sign-in row in profile' (#179) from feature/hide-current-host-signin-row into development 101a3f118c

Merge pull request 'fix(ui): poll for out-of-band email confirmation' (#180) from feature/email-confirm-poll-fallback into development 16349f5ad9

Merge pull request 'fix(ui): hold info toast ~1s before it rises and fades' (#181) from feature/toast-hold-before-fade into development ac383880b7

feat(banner): per-campaign colour overrides and urgent alerts ... 6db9178449

Non-default campaigns gain an optional colour override (background / text /
link) in two sets — one for every theme, one for the dark theme only — and an
"urgent" flag.

- Colours ride profile.get as six trailing FlatBuffers strings on
  BannerCampaign (backward-compatible). The client resolves the cascade
  (dark <- dark ?? all, light <- all) per rendered theme and derives the strip
  border from the background in JS (no CSS color-mix, for the old Android
  WebView floor); AdBanner applies them as inline vars scoped to the strip.
- Urgent is resolved entirely server-side: while any enabled, in-window urgent
  campaign exists, computeActiveSet returns only the urgent campaigns and
  bannerFor skips the eligibility gate — so a system notice reaches every viewer
  (paid / hint-holding / no_banner included) and preempts the ordinary feed. No
  wire field; it appears on each viewer's next profile.get.
- Admin console (/_gm/banners): native colour pickers + a live light/dark
  preview of the strip, and an urgent toggle. The default campaign stays plain,
  enforced by the service and a DB CHECK.

Migration 00009 is additive (nullable colour columns + a bool default +
all-or-nothing / hex / default-plain CHECKs) — expand-contract, rollback-safe.

Docs: ARCHITECTURE §10, UI_DESIGN, FUNCTIONAL (+ru). Tests: ads unit (urgent
preempt + colour validation), codec + resolver unit, gateway transcode, and
integration (colour round-trip + urgent bypass against real Postgres).

Merge pull request 'feat(banner): per-campaign colour overrides and urgent alerts' (#182) from feature/banner-colors-urgent into development d61ba68e9b

owner approved these changes 2026-07-05 14:10:07 +00:00

developer merged commit a9d0986e74 into master 2026-07-05 14:10:25 +00:00

Sign in to join this conversation.

Reviewers

No Reviewers

owner

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

owner (Ilia) developer

No Assignees

2 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: developer/scrabble-game#183