Out of office: jcoffey-dev is traveling from November 1 to November 6. Responses to issues may be slow or delayed during this time, but I will be checking in.
Cherry-pick of the store version mark from main. It applied cleanly, since the migration crate is identical on both branches. 2026.x writes the same version 1 as 27.1, and it refuses a store a later release has marked newer, so rolling back from a future 27.x can't open a store it no longer understands.
This isn't a security fix, so there's no release just for it. It rides along with the next 2026.x security release. store_version passes on RocksDB.
Cherry-pick of the store version mark from main. It applied cleanly, since the migration crate is identical on both branches. 2026.x writes the same version 1 as 27.1, and it refuses a store a later release has marked newer, so rolling back from a future 27.x can't open a store it no longer understands.
This isn't a security fix, so there's no release just for it. It rides along with the next 2026.x security release. `store_version` passes on RocksDB.
The store now carries an inbuxa store version (1), kept in the fork's
subspace beside the 0.16 schema version, which stays as it is. A store
without the mark, from an older release or from Stalwart, gets it on
start. A store marked newer than the running release is refused before
anything writes to it, with a message pointing at the newer release or
the pre-upgrade backup.
Layout 1 is what 2026.x and 27.1 both write today, so the same check goes
to release/2026: a 2026.x release then refuses a store a later 27.x has
changed instead of opening it.
(cherry picked from commit f7ec11c107)
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.
Cherry-pick of the store version mark from main. It applied cleanly, since the migration crate is identical on both branches. 2026.x writes the same version 1 as 27.1, and it refuses a store a later release has marked newer, so rolling back from a future 27.x can't open a store it no longer understands.
This isn't a security fix, so there's no release just for it. It rides along with the next 2026.x security release.
store_versionpasses on RocksDB.