Block a user
security upgrade
yeah you're right! -z checks the variable is empty, but since pg doesn't rewrite it to an empty string, the check never passes
security upgrade
ok! got the set -u back by providing default empty values to variables that could be unset
fix: set umask closes #6
Do you also want to add a release note to signal what's going on for upgraders?
this is done after merging to main right?
fix: set umask closes #6
i don't know how to provide a migration, running a chmod on the entrypoint would be ok?
i did this