§00Changelog
Every version, and what it changed for you.
63 releases since 25 Jul 2026. Breaking changes say what to do about them, and a version that rebuilds your index says so at the top.
Archis updates itself: chi update checks what is published, verifies the release hash before writing anything, and puts the previous binary back if the new one does not start. chi update --check installs nothing.
0.52.00.51.00.50.00.49.00.48.00.47.00.46.10.46.00.45.00.44.00.43.00.42.10.42.00.41.10.41.00.40.00.39.00.38.00.37.00.36.40.36.30.36.20.36.10.36.00.35.00.34.00.33.00.32.00.31.00.30.00.29.00.28.00.27.00.26.00.25.00.24.00.23.00.22.00.21.00.20.00.19.00.18.00.17.00.16.00.15.00.14.30.14.20.14.10.14.00.13.00.12.10.12.00.11.00.10.10.10.00.9.00.8.00.7.00.6.00.5.00.3.00.2.00.1.0
0.41.1
Fixes an upgrade from 0.40.0 that failed on the first tool call of the first session.
- Fixed0.41.0 could not be upgraded into. Two columns were added to the session ledger without a schema version bump, and the migration that adds them runs only for a database written by an older version — so a database written by 0.40.0, which is already at the current version, never received them while a freshly created one had them from the start. The first session after updating answered
table exposures has no column named lifecycle, which is nearly every call Archis makes. The columns are now added when the database is opened, whatever version wrote it. Nothing was lost: the index and the session history were untouched throughout, and updating to 0.41.1 repairs the database on the next command.
- Fixed0.41.0 could not be upgraded into. Two columns were added to the session ledger without a schema version bump, and the migration that adds them runs only for a database written by an older version — so a database written by 0.40.0, which is already at the current version, never received them while a freshly created one had them from the start. The first session after updating answered
Run the current release
Archis Free is the whole local engine, with no card. Everything semantic runs on your machine — there is no endpoint that accepts source.