Cherry-pick of #329 (c987a5a, clean), so that a rollback from 27.1 to 2026.x keeps its administrator roles. 27.1 grants permissions 690–695 to the stored administrator roles, and before this change a 2026.x build couldn't load a role holding them.
It rides the next 2026.x security release; it doesn't get a release of its own, the same as the store mark reader (#247).
Tested on this branch: registry tests (the new test passes); fmt and fork checks; cargo build -p inbuxa and cargo test --workspace --no-run. Also a Role pickled on main with permissions 690, 694 and 695 (enabled and disabled) loads here, keeping only the permissions this build knows.
Cherry-pick of #329 (c987a5a, clean), so that a rollback from 27.1 to 2026.x keeps its administrator roles. 27.1 grants permissions 690–695 to the stored administrator roles, and before this change a 2026.x build couldn't load a role holding them.
It rides the next 2026.x security release; it doesn't get a release of its own, the same as the store mark reader (#247).
Tested on this branch: registry tests (the new test passes); fmt and fork checks; `cargo build -p inbuxa` and `cargo test --workspace --no-run`. Also a Role pickled on main with permissions 690, 694 and 695 (enabled and disabled) loads here, keeping only the permissions this build knows.
A stored object's permission list, event list or enum-keyed map failed
to load whole when it held a value the running build didn't know. A
newer release grants its new permissions to the administrator roles it
finds, so after an upgrade an older build could no longer read those
roles, and a rollback lost every administrator's permissions (the
recovery admin still worked).
Lists and enum-keyed maps now leave out a value they don't recognize,
read past it, and load the rest of the object. A damaged stream is
still refused. A role edited and saved on the older build keeps only
the permissions that build knows.
Test: a Permission list and an enum-keyed map holding an id from a
newer build failed to read on main; now the unknown entries are left
out, the known ones and the field after them read, and a list cut
short is still refused.
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 #329 (
c987a5a, clean), so that a rollback from 27.1 to 2026.x keeps its administrator roles. 27.1 grants permissions 690–695 to the stored administrator roles, and before this change a 2026.x build couldn't load a role holding them.It rides the next 2026.x security release; it doesn't get a release of its own, the same as the store mark reader (#247).
Tested on this branch: registry tests (the new test passes); fmt and fork checks;
cargo build -p inbuxaandcargo test --workspace --no-run. Also a Role pickled on main with permissions 690, 694 and 695 (enabled and disabled) loads here, keeping only the permissions this build knows.