v0.17.1

Added

• Administrators can pin the default VTA image from the Defaults page.

Changed

• The Trust Agent creation form preselects and labels the administrator-pinned
  image, falling back to the image tagged latest when no valid pin exists.

Requires vtafarm-api 0.17.1.

v0.17.0

Added

• Users can sign in with a Keyring identity by scanning a QR code or opening
  Keyring on the same device, confirming the two-digit request number, and
  choosing the Farm account when one identity can access more than one.
• Account settings list claim-derived Keyring sign-in identities and allow
  users to revoke an identity and the Farm sessions created through it.

Changed

• The home page and Get Started flow present clearer paths for creating a
  Trust Agent, setting up an account, signing in, installing Keyring, linking
  the agent, and joining the demo community.
• Frontend responses deny framing to protect sign-in and portal interactions.

Requires vtafarm-api 0.17.0.

v0.16.1

Fixed

• Failed Full Stack setup recovery includes the Trust Registry when it is
  enabled and selects an available Trust Registry image for the retry.

Requires vtafarm-api 0.16.1.

v0.16.0

Added

• Visitors can claim a pre-provisioned VTA through a guided public onboarding
  flow, open the claim in Keyring, compare the confirmation code, and continue
  to the FPDev community.
• Administrators can create public-signup pools, monitor available, reserved,
  and handed-out inventory, pause or resume public allocation, and add VTAs to
  an existing pool.

Changed

• The public landing page now leads visitors into the VTA onboarding journey
  while keeping account sign-in available.
• Updated React, React Router, Lucide, Vite, shadcn, and TypeScript ESLint
  dependencies.

Requires vtafarm-api 0.16.0.

v0.15.1

Fixed

• Same-device Keyring actions open the registered keyring:// app link while
  preserving the HTTPS trigger link in QR codes for camera scanning.
• Session status details and actions remain visible and usable on narrow mobile
  screens instead of overflowing the page.

Requires vtafarm-api 0.15.0.

v0.15.0

Added

• Users and administrators can optionally provision a Trust Registry when
  creating a Full Stack, or enable one later on an existing Full Stack.
• Trust Registry image selection, setup progress, failure recovery, component
  version details, and the resulting Registry DID are available in the portal.

Changed

• Capacity and resource-default views include the optional Trust Registry
  component when planning or configuring Full Stack deployments.

Requires vtafarm-api 0.15.0.

v0.14.2

Changed

• Updated Radix UI, Lucide, Vite, ESLint, and TypeScript ESLint tooling.
• Vite configuration uses native module paths when resolving source aliases.

Fixed

• Failed Keyring administrator requests show why the key could not be added and
  prompt users to generate a new QR code before trying again.

Requires vtafarm-api 0.14.2.

v0.14.1

Added

• Users and administrators can recover sessions that fail during component
  deployment by selecting image versions and continuing setup without deleting
  persistent data or repeating completed setup jobs.

Changed

• Version-change previews show current and target images and distinguish
  upgrades, downgrades, and other image changes.

Fixed

• VTA pool, load-testing, and session-upgrade image pickers consistently show
  labeled image metadata in viewport-aware dropdowns.
• Failed creation screens direct users to the agent detail page to recover the
  agent when possible or delete it when necessary.

Requires vtafarm-api 0.14.1.

v0.14.0

Added

• Administrators can create and monitor batches of pre-provisioned VTAs, hand
  them out through QR-based claim stations, retry failed preparation, and clean
  up unused inventory.
• Container image selectors identify latest, nightly, and main builds and
  show each image's build date.

Fixed

• Image selector dropdowns remain usable with long image tags and limited
  viewport space.

Requires vtafarm-api 0.14.0.

v0.13.0

Added

• Keyring connections use VTI trigger links that can be opened directly on the
  same device or scanned as a QR code.
• Claiming a VTA now requires comparing a short code and explicitly confirming
  or rejecting the Keyring before initial provisioning or adding another
  administrator.

Changed

• Removed VTA Browser Plugin account sign-in and linked-identity management;
  account authentication continues to use passkeys.
• Updated React, SimpleWebAuthn, Tailwind CSS, shadcn, and TypeScript tooling.

Requires vtafarm-api 0.13.0.