You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Added optional Touch ID unlock for encrypted workspaces in provisioned Developer ID releases.
The release pipeline now embeds the Developer ID provisioning profile required for the Keychain access group entitlement.
Local unsigned development builds continue to use the master password only.
GateTree 2.1.2
First-run workspace setup
Fixed the workspace-folder picker on a fresh installation when the suggested GateTree folder does not yet exist.
GateTree 2.1.1
Deployment workflow
Added direct Jira and CX API integration backed by KeePass credentials.
Added CX readiness validation, per-role approval and deny actions, and queue-manager restart recovery.
Improved deployment reports with validation/deployment details, version, target IPs and failure context.
Added Vault configuration, integrated help, updated deployment queue layout and new Sauron/Olympos connections.
GateTree 2.1.0
Ansible deployment queue and Jira reporting
Added Jira availability checks and deployment lifecycle updates to the configured deployment process.
Deployment reports now retain validation, Queue Manager events and Ansible deployment output in one HTML report stored in the encrypted workspace.
Successful Jira deployments upload the report as an attachment and link it from the deployment result comment.
Queue Logs now presents the combined report and can save it as HTML.
Improved target extraction so every host name and IP address from Ansible preview output is retained.
GateTree 2.0.0
Encrypted workspace and setup
Choose a workspace folder on first launch and create a mandatory master password.
Workspace data is stored in SQLCipher, including Connections, Vault references,
Notes, deployment configuration/history/queue/logs, AI settings, Quick Access,
and the latest bulk validation result.
The chosen folder is remembered. Existing encrypted workspaces require both gatetree.sqlite and its original gatetree.sqlite.salt file.
Plaintext workspace mode is no longer supported.
Configuration export and import
File → Export Configuration creates a full, versioned plaintext JSON export of
the application database. Protect this file: it contains private configuration,
notes, connection details and operational history.
File → Import Configuration restores that JSON into an unlocked encrypted
workspace. An encrypted backup is created before replacement; failed imports
roll back. Column order differences between database versions are supported.
Fresh setup: choose an empty folder → set a master password → import JSON.
Exports exclude the master password, external KeePass databases and passwords,
external files/tools, and macOS UI preferences. Reconnect KeePass and adjust
machine-specific paths and permissions when restoring on another Mac.
Important upgrade information
Legacy Workspace.gatetree files are not imported automatically and are not
accepted by the JSON importer. Keep the previous app and original workspace
backup if you do not yet have a compatible JSON export.
An older 1.x SQL database alone may not contain its Connections and Vaults:
those versions also used the legacy workspace file. Do not discard that file.
Fully migrated SQLCipher workspaces can be opened directly by selecting their
containing folder. Quit GateTree before moving a complete workspace folder.
Verification
Tested a real JSON export through all 17 exported tables, including encrypted
database reopening, key rejection/rekey, and rollback checks.