Backports #322 (store check, inbuxa:StoreCheck), #323 (store snapshot, inbuxa:StoreSnapshot) and #333 (blob store change, inbuxa:BlobStoreChange) from main to the 2026 series. Each merge was cherry-picked from main (#324f2bd0cf, #32877111f9 and #3355a0034e), and the three are squashed into one commit, since a single pick doesn't build on its own here.
Changes needed for this series:
Ids: The permissions stay at ids 695 to 697 and the store.blob-read-through event stays at 660, the same as in 27.1, because stored settings refer to them by id. That way a store that moves between the series keeps their meaning, together with #331. This series doesn't have 27.1's Relay and Migration ids (permissions 690 to 694, events 650 to 659), so Permission::COUNT and TOTAL_EVENT_COUNT run past a gap. The default-permissions loop now skips ids it doesn't know instead of unwrapping, and the event-id test allows the 10 unused ids.
json_to_value: 27.1 keeps it in the relay module, which this series doesn't have, so here it is in its own crates/jmap/src/inbuxa/json.rs.
Privacy catalog: the vocabulary gains data-directory, which the store snapshot uses.
Schema: the permission and event entries were added to this series' schema.json.gz, and its sha was recomputed.
Checks:
cargo build -p inbuxa --locked
cargo test --workspace --locked --no-run
Unit tests in store, trc, registry, common, services, features and jmap, including the event-id test and the key-letter tests: all passed.
Fork checks: name, notice, context, privacy, expr-schema and their unit tests.
Integration tests store_check_tests, store_snapshot_tests and blob_store_change_tests on RocksDB, with the default blob store and with BLOB_STORE=FileSystem: all 6 passed.
After merge, these ship in the next 2026.x patch (after v2026.11.9).
Backports #322 (store check, `inbuxa:StoreCheck`), #323 (store snapshot, `inbuxa:StoreSnapshot`) and #333 (blob store change, `inbuxa:BlobStoreChange`) from main to the 2026 series. Each merge was cherry-picked from main (#324 f2bd0cf, #328 77111f9 and #335 5a0034e), and the three are squashed into one commit, since a single pick doesn't build on its own here.
Changes needed for this series:
- **Ids:** The permissions stay at ids 695 to 697 and the `store.blob-read-through` event stays at 660, the same as in 27.1, because stored settings refer to them by id. That way a store that moves between the series keeps their meaning, together with #331. This series doesn't have 27.1's Relay and Migration ids (permissions 690 to 694, events 650 to 659), so `Permission::COUNT` and `TOTAL_EVENT_COUNT` run past a gap. The default-permissions loop now skips ids it doesn't know instead of unwrapping, and the event-id test allows the 10 unused ids.
- **`json_to_value`:** 27.1 keeps it in the relay module, which this series doesn't have, so here it is in its own `crates/jmap/src/inbuxa/json.rs`.
- **Privacy catalog:** the vocabulary gains `data-directory`, which the store snapshot uses.
- **Schema:** the permission and event entries were added to this series' schema.json.gz, and its sha was recomputed.
Checks:
- `cargo build -p inbuxa --locked`
- `cargo test --workspace --locked --no-run`
- Unit tests in store, trc, registry, common, services, features and jmap, including the event-id test and the key-letter tests: all passed.
- Fork checks: name, notice, context, privacy, expr-schema and their unit tests.
- Integration tests `store_check_tests`, `store_snapshot_tests` and `blob_store_change_tests` on RocksDB, with the default blob store and with `BLOB_STORE=FileSystem`: all 6 passed.
After merge, these ship in the next 2026.x patch (after v2026.11.9).
Brings #322 (inbuxa:StoreCheck), #323 (inbuxa:StoreSnapshot) and #333
(inbuxa:BlobStoreChange) from main to the 2026 series.
Fitted to this series:
- Permission ids stay 695 to 697 and the store.blob-read-through event
stays 660, as in 27.1: stored settings name them by id, so a store
moved between the series keeps their meaning. This series lacks 27.1's
Relay and Migration ids (690 to 694, events 650 to 659); the default
permissions loop skips the gaps and the event id test allows them.
- json_to_value, which 27.1 keeps in its relay module, is in
crates/jmap/src/inbuxa/json.rs.
- The privacy catalog vocabulary gains "data-directory".
(cherry picked from commit f2bd0cf, 77111f9 and 5a0034e)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Backports #322 (store check,
inbuxa:StoreCheck), #323 (store snapshot,inbuxa:StoreSnapshot) and #333 (blob store change,inbuxa:BlobStoreChange) from main to the 2026 series. Each merge was cherry-picked from main (#324f2bd0cf, #32877111f9and #3355a0034e), and the three are squashed into one commit, since a single pick doesn't build on its own here.Changes needed for this series:
store.blob-read-throughevent stays at 660, the same as in 27.1, because stored settings refer to them by id. That way a store that moves between the series keeps their meaning, together with #331. This series doesn't have 27.1's Relay and Migration ids (permissions 690 to 694, events 650 to 659), soPermission::COUNTandTOTAL_EVENT_COUNTrun past a gap. The default-permissions loop now skips ids it doesn't know instead of unwrapping, and the event-id test allows the 10 unused ids.json_to_value: 27.1 keeps it in the relay module, which this series doesn't have, so here it is in its owncrates/jmap/src/inbuxa/json.rs.data-directory, which the store snapshot uses.Checks:
cargo build -p inbuxa --lockedcargo test --workspace --locked --no-runstore_check_tests,store_snapshot_testsandblob_store_change_testson RocksDB, with the default blob store and withBLOB_STORE=FileSystem: all 6 passed.After merge, these ship in the next 2026.x patch (after v2026.11.9).