When using ALTER DEFAULT PRIVILEGES (without specifying a FOR ROLE) and running with the embedded postgres, something goes wrong and pgschema wants to revoke default privileges on the postgres role and add them to a (non-existant) pgschema role.
Trying to solve this by making FOR ROLE postgres explicit doesn't work either, because then pgschema fails with "role postgres does not exist".
I can sort-of work around that by making the role explicit and running in an external planning database, but even there it seems to me I fail on the second run - though that might be another issue. Still looking into that.