Registry: a stored list skips values this build doesn't know (release/2026) #331

Merged
jcoffey-dev merged 1 commits from fix/skip-unknown-enum-ids-2026 into release/2026 2026-11-09 06:30:29 +00:00
1 Commits
Author SHA1 Message Date
jcoffey-dev da39fbf52c Registry: a stored list skips values this build doesn't know
ci / fork-checks (pull_request) Skipped
ci / build (pull_request) Skipped
github/ci (branch) GitHub Actions
ci / github (pull_request) Successful in 9m6s
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.
2026-11-08 23:02:46 -07:00