Release history

AutoNexit application changes

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

Version

v1.45.1 Reliable task editor uploads

Released on

Images, documents and videos now finish attaching correctly when remote storage completes through the transfer queue.

What changed

  • Queued transfers now apply task-specific validation and link each verified file exactly once, even when the task changes while the upload is in progress.
  • Stale uploads are rejected before reserving storage, and the editor now gives localized explanations for version, quota and unsupported-content failures without the unwanted separator line.
Version

v1.45.0 In-app project invitations and compact storage cards

Released on

Project invitations can now be reviewed, accepted or declined inside AutoNexit, and account storage opens each project from one compact card.

What changed

  • Invitation notifications and Telegram buttons open a protected in-app decision dialog; declining invalidates the link, records an audit event and notifies the inviter.
  • Member activity loads through its JSON API without an Inertia page error, while storage cards show only project name and code, project usage and creation date and open the project repository when selected.
Version

v1.44.0 Complete managed-project access removal

Released on

Add user can now remove an existing user from every project the operator manages in one controlled action.

What changed

  • The removal revokes project roles, shared-section and financial permissions, controllable workspace-derived project access and pending project invitations immediately while retaining historical project records.
  • The operation is tenant-scoped, transactional, audited and idempotent; project managers and workspace owners must transfer responsibility before their access can be removed.
Version

v1.43.0 Reliable task media and clearer conversations

Released on

Task discussions now use compact, readable message cards, while images, documents and local videos can be uploaded and displayed safely inside the task editor.

What changed

  • Conversation entries show the author, avatar, message and time in a balanced scrollable panel with a compact composer.
  • Task editor uploads now return their verified media type and signed preview; images and local MP4 or WebM videos render in place, documents remain downloadable, and mismatched file content is quarantined.
Version

v1.42.0 Controlled task editing and compact details

Released on

Task details now open as a bounded dialog, preserve unsaved work in the browser and save to the server only on explicit request.

What changed

  • The redundant detail tabs are removed; description, compact attachments and conversation remain together, dates use separate rows, and task attachments can be removed through an audited version-safe action.
  • Unsaved task edits stay in this browser and closing offers save, keep-draft or continue choices. Date-time pickers default omitted time to 09:00 and conversion respects the user time zone.
Version

v1.41.1 A denser, clearer task workspace

Released on

Task details now match the intended compact workspace: editing stays central while reminders, assignees and recent activity remain close at hand without consuming whole pages.

What changed

  • The task workspace now has three focused content tabs, a wider grouped settings rail, a dominant description editor, and stable side-by-side file and conversation panels.
  • Reminders, assignees and activity use compact expandable rail sections; activity entries no longer stretch into oversized empty cards, and the layout remains usable in Persian right-to-left and on smaller screens.
Version

v1.41.0 Project-wide reminders and a focused task workspace

Released on

A reminder can now notify every active project member, while task details use a denser full-screen layout that keeps editing, files, discussion and settings in view.

What changed

  • The Notify selector adds Everyone; one audited reminder fans out personal, localized notifications to the active project membership when it becomes due, and recurring occurrences retain the same audience.
  • Persian reminder examples align from the right, and the task detail surface now uses a fixed compact header, grouped settings rail, large editor and adjacent file and conversation panels without adding or removing task capabilities.
Version

v1.40.1 Clear reminder controls in every theme

Released on

Project reminder actions and forms now remain clearly visible in light and dark themes, including Persian right-to-left layouts.

What changed

  • The reminder page now uses AutoNexit’s shared surface, text, border and accent tokens, restoring solid dialog surfaces and high-contrast primary and secondary actions.
  • Browser regression coverage verifies the reminder dialog and its main action in both light and dark themes so undefined visual tokens cannot make controls transparent again.
Version

v1.40.0 Project Office and actionable Telegram notifications

Released on

Reminders, notes and project tasks now live together in Project Office, while Telegram notifications open their exact AutoNexit destination from an inline action button.

What changed

  • Project Office adds a project-scoped reminder center with Today, Upcoming and Completed views, localized Persian or Gregorian date selection, member assignment, recurring schedules, completion, snoozing and audited version-safe edits.
  • Existing Notebook and Project Task links remain compatible and redirect to their new Project Office locations; due reminders use the existing scheduler and notification preferences, and safe application notification targets now appear as Telegram inline buttons.
Version

v1.39.0 Independent Commercial change requests

Released on

Commercial change requests now form a dedicated revenue-focused register while retaining an optional traceable link to Lifecycle modifications.

What changed

  • Commercial teams can create, review, approve and archive their own customer-facing change records with quoted revenue, estimated cost, projected margin, schedule impact and supporting files.
  • An existing Lifecycle modification can seed technical context into a snapshot without coupling later Commercial edits to the engineering workflow; previous financial impacts are migrated safely.