## 0.76.1

- **A release bundle no longer carries the permissions of the machine that packed it.** 0.76.0 was
  published from a host whose umask was 077, so the bundle's own directories went into the tarball
  at 0700. `install.py` copies that tree onto the deployment with its modes intact, the containers
  run as uid 10001, and the worker died on its first job lookup with a permission error naming a
  file that is plainly there: an upgrade to 0.76.0 left a deployment part way, with the rollback
  text printed and the backup taken. Nothing between the packer and the client could see it,
  because `MANIFEST` covers file CONTENT and a correct digest for a file says nothing about the
  mode of the directory holding it. `scripts/promote-release.py` now normalises what it publishes,
  directories and executables 0755 and everything else 0644, owned by root, so the same bundle
  packs identically whoever packs it; and `deploy/install.py` no longer depends on the packer's
  umask on install or on upgrade, because a deployment installs whatever bundle it was handed,
  including bundles packed before this release existed. **Anyone who installed or upgraded to
  0.76.0 should upgrade to this release.**