Skip to content

Ork 1.2.1

Choose a tag to compare

View all tags
@raxon raxon released this 09 Nov 16:58
v1.2.1
5c5f20c
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Ork 1.2.1

Ork 1.2.1 brings server and app version information into settings and adds update controls for supported self-hosted servers. It also includes the desktop, Accounts, onboarding and reliability work prepared since the previous release.

Updates

  • See the installed app version and connected server version in settings.
  • Choose Stable or Beta for desktop updates and supported self-hosted server updates. Beta also receives newer stable releases.
  • Request a server update from the desktop or mobile app when a release is available. The server owner can also enable automatic updates.
  • If a client and server cannot use the same protocol, Ork opens an update screen instead of the workspace.

More in this release

  • Connect and authorize self-hosted servers through Accounts, including servers that already contain a workspace.
  • Set up a server with the Linux installer, or pair an existing server with a desktop or mobile app.
  • Use the Tauri desktop app on macOS, Windows and Linux. On macOS and Linux, bots can use the app-managed host computer after you grant access.
  • New Spaces and organizations finish onboarding with their own bot. Mobile also preserves unsent messages when a session is rejected.
  • Bots can transfer files between conversations, use explicit reply modes and show active routines in a conversation. Chat integrations can receive images.
  • OAuth refresh and worker recovery are coordinated so unrelated recovery work can continue when housekeeping stalls.

Self-hosted servers

New installer-based deployments set up the server updater. Existing installations need operator setup before update controls become available. Back up the database, server configuration and bot data before upgrading. Restoring an earlier image does not reverse database migrations.

The updater needs access to the host Docker socket. It accepts update requests only from the delegated server owner and deploys releases through its private control interface. If an update result cannot be confirmed, check the server before trying again.

Signed Preview installations can receive Stable through their existing update feed when the signing key matches. Diagnostic builds with updates disabled require a new installer. Switching to Stable does not replace a newer installed beta with an older release.

See the self-hosting guide and upgrade guide.

Licensing

Ork is source-available. Existing Apache-licensed material and third-party notices remain in place. New original Ork work is covered by PolyForm Noncommercial 1.0.0. See LICENSE.md for the scope and terms. The commercial agreement and contributor agreement remain drafts.

Assets 12
Loading