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
- Verified live analysis commands against the current unified Magellan database after the temporal schema rollout.
15
+
16
+
### Changed
17
+
18
+
-**Release docs refresh**:
19
+
- Updated README and manual requirements to reflect current Magellan schema support and removed stale 4D-coordinate migration guidance from the public path.
20
+
8
21
## [1.8.1] - 2026-06-20
9
22
10
23
### Added
@@ -28,6 +41,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
28
41
- CFG/status compatibility cleanup:
29
42
-`DatabaseStatus.cfg_edges` remains a normal compatibility field for Magellan-backed status output instead of being marked deprecated while still in active use.
30
43
- Legacy in-memory `coord_*` fields are now documented as analysis-time values, not persisted database columns.
44
+
- Dynamic schema version alignment:
45
+
- Updated `REQUIRED_SQLITEGRAPH_SCHEMA_VERSION` to dynamically reference `sqlitegraph::schema::SCHEMA_VERSION as i32` instead of hardcoding `3`, aligning with sqlitegraph v3.3.1 (schema v6).
31
46
- Source hygiene cleanup:
32
47
- Removed a dead AST CFG builder field and cleaned up stale doctest placeholders that used `unimplemented!()`.
33
48
- Replaced stale wording that implied temporary or 4D-backed behavior where Mirage now only reads Magellan-managed CFG data.
- Run `magellan watch --root ./src --db .magellan/mirage.db` first
48
49
-**Rust 1.70+**
49
50
50
-
### Magellan v10 → v11 Migration
51
+
### Magellan Schema Compatibility
51
52
52
-
If you're upgrading from Magellan v10 to v11, follow these steps:
53
+
Mirage reads Magellan-managed CFG data and does not require Magellan's temporal tables directly, but it is verified to open current schema-v18 databases cleanly.
53
54
54
55
```bash
55
-
#1. Check your current Magellan schema version
56
+
# Check the embedded Magellan schema version
56
57
mirage status --db .magellan/mirage.db
57
-
#Look for: "Schema version: 1 (Magellan: X)"
58
+
#Example: "Schema version: 1 (Magellan: 18)"
58
59
59
-
#2. If it shows v10 or earlier, rebuild your Magellan database
60
+
# If the database is too old, rebuild it with current Magellan
0 commit comments