Reference
Updates
How agex checks for and installs new releases, and what its version numbers mean.
How agex checks for updates
agex asks GitHub for its latest release a little after it launches, and again every six hours. To check right away, choose Agex › Check for Updates…, or run Check for Updates… in the command palette (⇧⌘P).
Install an update
When a newer release is out, an Update button appears in the top bar.
- Click Update. agex downloads and installs the new release in the background while you keep working.
- Click Restart to update to switch to it.
A copy of agex that isn't installed as an app opens the release page instead.
Update from the command line
| Command | What it does |
|---|---|
agex update --check | Says whether a newer release is out, and which version you have. |
agex update | Downloads and installs the latest release over the installed app. |
agex version | Prints the version you're running. |
If agex is running when agex update finishes, quit and reopen it to switch to the new version.
$ agex update --check
agex 2.8.0 is out (this is 2.7.123)What version numbers mean
agex uses pride versioning. A version has three parts, vPROUD.DEFAULT.SHAME, like v2.7.123:
| Part | Goes up when | Resets |
|---|---|---|
| PROUD | A release is marked as one to be proud of. | DEFAULT and SHAME go back to 0. |
| DEFAULT | A release adds a feature. | SHAME goes back to 0. |
| SHAME | A release brings fixes and other changes. | Nothing. |
Each change since the last release bumps one part, so a release with several fixes raises SHAME by more than one, and numbers can skip. A small feature can also count as a SHAME bump.
A higher version is always newer: compare PROUD first, then DEFAULT, then SHAME.