mait.sh1.142.0

Private beta: features and content may change. No warranty; use at your own risk.

Project

Changelog

Every release of every product in one feed, newest first. Search it, or filter by product.

Releases

Find a release.

VaaS Server

Latest release 0.9.3

Documentation

51 releases

November 2026

  1. 0.9.3
    • Maintenance release.

October 2026

  1. 0.9.2
    • Maintenance release.
  2. 0.9.0
    • Monitoring now reports daily response times and session totals for the latest completed day, and the summaries survive restarts.
    • Metrics and daily totals now carry the release channel label.
  3. 0.8.5
    • Rolling the image back to this version or later after a newer version has upgraded the database now starts normally instead of failing at startup.
  5. 0.8.3
    • Attaching to a mesh network with a requested address that is not valid is now refused with a client error instead of being ignored.
    • A hub-change report received from another relay is accepted but reported as not applied, because each relay elects its own hub.
    • The Helm chart now lists the container-mesh settings with their defaults.
    • Updated shared components.

September 2026

  1. 0.8.0
    • New vaas-server legal command lists the copyright line and the third-party components built into the server, with optional full notice texts or JSON and Markdown output.
    • Container-mesh networks now belong to one account: attaching with a network name or peer id that another account already uses is refused.
  3. 0.7.0
    • Every authenticated request and relay connection now checks the current account and credential status; disabled accounts or withdrawn credentials are refused, and relays in progress end within seconds.
    • When account status cannot be confirmed, protected requests are refused with a temporary-unavailability response instead of being allowed.
  4. 0.6.3
    • Added the container mesh control plane: network membership with heartbeat leases, automatic address allocation, hub election and hub-published names.
    • Deployments stop the old instance before starting the new one, so each upgrade has a brief interruption instead of two instances writing the same data.
  5. 0.6.2
    • Maintenance release.
  6. 0.6.1
    • Fixed storage permissions that could stop the service from writing its session records after an upgrade.

August 2026

  1. 0.6.0
    • Added daily session totals without customer identifiers, kept after detailed session records reach their retention limit.
  2. 0.5.6
    • The scheduled cleanup of old session records now reaches the service reliably.
  3. 0.5.5
    • The scheduled cleanup job runs with the same restricted security settings as the service.
  5. 0.4.2
    • Pairing tokens are no longer written to service logs.
  6. 0.4.3
    • Maintenance release.
  7. 0.4.0
    • Added session activity records and metrics for connection attempts, access refusals and session duration, with a seven-day default retention.
  9. 0.3.15
    • Credentials without VaaS access are now refused instead of being allowed to connect.

July 2026

  2. 0.1.141
    • First published release: authenticated relay pairing, customer and administrative session list and drop, and a health check that reports version and build commit.
  3. 0.3.0
    • Maintenance release.
  4. Early development
    • Summary of early development since 2026-02-23, before tagged releases began.
    • Client and administrative session APIs for the relay, with an OpenAPI specification.
    • Multi-environment and cross-architecture deployment support.
    • Coordinated versioning with the VaaS CLI so client and server stay paired.
    • Verbose/debug logging and build-commit reporting for support.