Elyra
 Elyra The coding agent eTerm The terminal that knows where each command ends Starf An activity monitor for Apple silicon that never invents a number Litr A small, native web browser for macOS Notr A notebook for macOS e The native code editor Elyra Grove Native local development environment Askr The real server for Laravel & PHP Elyra Framework Rust + Svelte 5 framework for desktop apps Elyra Conductor Local project conductor Refr Local-first PDF workspace for macOS Elyra SQL Server MySQL-compatible SQL server in Rust Elyra Félagi Agents as teammates on one board Elyra SQL Client Native desktop SQL workbench Elyra SQL Anywhere Replication-ready SQL engine Elyra Sjá SEO & GEO workspace for macOS Elyra DataGrid Server-driven data grid for Laravel
Start here
Getting started
Installation
Updating
Editing
Editing
Navigation
Find & replace
Languages & LSP
Workflow
Laravel
Inertia & VILT
Terminal
Tasks & tests
Source control
Database
Debugging
AI agents
Agent workspace sync
Reference
Configuration
Keybindings
Keyboard shortcuts
Troubleshooting
Release notes
Changelog
Elyra
Elyra
e
Updating

Updating

e has a built-in auto-updater backed by GitHub Releases.

How it works

  • On startup (at most every six hours), e quietly checks for a newer release. It reads the version from where github.com/kwhorne/e/releases/latest redirects to and the notes from that tag's CHANGELOG.md — not from the GitHub API, whose 60 unauthenticated calls an hour per address a day of restarts (or an office behind one IP) uses up. The API is only a fallback.
  • When one is available, a notice appears in the bottom-right corner with the release version and a What's new toggle that expands the changelog.
  • Click Update now to download the build for your platform and replace the running binary in place.
  • After it installs, click Restart now to relaunch into the new version.

Manual check

Run Check for Updates from the command palette (⌘⇧P). If you're already on the latest version, you'll see a confirmation.

Notes

  • The updater downloads the asset for your platform (e-<target>.tar.gz) from the release's download URL, verifies it against the .sha256 published beside it, and swaps the binary atomically.
  • If a download fails, the notice offers Retry.
  • Updates are opt-in: nothing is installed until you click Update now.

For maintainers

Releases are produced with:

./scripts/release.sh X.Y.Z

This bumps the version, moves the Unreleased section of CHANGELOG.md under a new dated heading, commits, tags vX.Y.Z, and pushes. A GitHub Actions workflow then builds and attaches the per-platform binaries to the release, which the auto-updater consumes.

Back to docs