Release history

AutoNexit application changes

Follow user-visible improvements, fixes, and compatibility changes across each published version.

Version

v1.1.0 Client, membership, profile, and storage workspace

Released on

Project collaboration is clearer with dedicated client forms, controlled invitations, member activity, profile photos, and a shared storage overview.

What changed

  • Added project member invitations and management, visible collaborators, cropped profile photos, decimal 500 MB account quotas, and per-project storage usage.
Version

v1.0.4 Production regression hardening

Released on

Authentication, project passports, task documents, handover packages, release context, and remote paths now satisfy their production contracts.

What changed

  • Completed email-verification recovery paths, selected handover generation, rich task-document persistence, public passport throttling, application release context, and date-first user storage paths.
Version

v1.0.3 Production Web Push runtime assurance

Released on

Production packages now prove that the Web Push library and VAPID key generator are present before release.

What changed

  • Added a fail-closed release check for the installed package, VAPID class and method, and successful key-pair generation without exposing generated keys.
Version

v1.0.2 Project passport access restored

Released on

Project passport pages now open reliably with the correct project-scoped publishing permissions.

What changed

  • Fixed the project passport page route and completed its publishing authorization contract.
Version

v1.0.1 Date-first remote user folders

Released on

New user-owned FTP objects are grouped by UTC date before their user folder.

What changed

  • Changed new remote paths to users/year/month/day/user while preserving every existing stored path.
Version

v1.0.0 First tracked AutoNexit release

Released on

A stable version baseline for the connected industrial automation project workspace.

What changed

  • Strengthened the complete email registration, verification, sign-out, and return-login journey.
  • Made the active project name visible throughout project pages and the application version visible elsewhere.
  • Introduced this localized public release history as the permanent source for product changes.