The first checked deploy rolled back because the web server could not write to storage/repositories inside the release. That folder is a leftover: repositories live in REPOSITORY_STORAGE_ROOT, which is the shared folder outside the release, and the deploy does not share the leftover. The self-check behind /deploy-check now tests only the folders under storage/ and public/uploads/ that are links into the shared folder, which are the ones the site writes to.
Fixed the deploy check failing on a folder the site does not use
The self-check now tries to write only to the folders the deploy shared, so a folder left inside the release, such as storage/repositories, no longer rolls a deploy back.