Releases / 0.2.2

Release 005

Release 005 · VEX 0.2.2

Fresh releases, minutes after they ship.

A small, fast follow up to 0.2.1 with one job: when a new VEX version is out, you should know about it in minutes, not the next day.

This page summarizes the work merged since 0.2.1.

The ambient update check · Rebuilt

5

Minutes between checks, on start, on window focus, and on every tick while VEX runs. The old check fired four times a day.

A day of update checks, four against two hundred and eighty eight

01 · Updates

Minutes, not the next day.

VEX now checks for a new version on start, on window focus, and every five minutes while it runs. The check downloads a few small release metadata files and does nothing else: auto download and auto install stay off, and the availability banner remains the only effect. Installing is always your click.

01

A five minute cadence. The previous ambient check throttled itself to once every six hours, so a fresh release could sit unnoticed for most of a day. Now every five minute tick may check, guarded by a persisted four minute success throttle so bursts still collapse into one request.

02

Never over an active download. A check refuses to run while an update is downloading, downloaded, or installing, and the guard is verified twice, before and after the asynchronous preferences read, so a download you start in that gap is never interrupted. Late results from a silent check cannot rewind an active state either.

03

No nagging. Silent checks are invisible unless they find something. A dismissed error banner stays dismissed while the feed is broken, and retries back off exponentially, ten minutes doubling up to a two hour cap, resetting the moment a check succeeds. The per version Later snooze is unchanged: snoozing one version never hides a newer one.

This release rebuilds that ambient check around the five minute goal and hardens it against the races and the nagging a faster cadence could otherwise have introduced.

02 · Engineering

Under the hood.

The root test suite now passes on a machine with no configured wallet and no local fixtures, closing the environment coupling failures CI surfaced after 0.2.1.

03 · Before you update

Upgrade notes.

No new database migrations ship in this release. No manual action is required. After updating, VEX itself will tell you about the next release within minutes of it going live.