Back to Changelog
Panel Backend
v1.0.439
Git Deploy: preserve list is saved, panel-owned files survive a deploy, rollback restores exactly
Bug Fixes
6- Saving a repository no longer loses its "Preserve on deploy" list — the field was assigned but never written to the database, so a saved list silently vanished and the next deploy still removed .env, storage and uploads.
- A deploy no longer deletes the panel-owned .user.ini or the .well-known/acme-challenge directory from the document root. Both are protected from removal while a repository shipping its own copy may still overwrite them; previously a deploy during certificate issuance could delete the challenge.
- Rollback now restores the target exactly. It used to unpack the snapshot on top of the current files, so anything a bad deploy added stayed behind and the rollback looked successful while the site was still broken. The preserve list and panel-owned files are honoured during the restore.
- Environment switches now do what they say. Protected refuses unattended deploys and blocks deletion until it is turned off; Auto deploy makes a webhook push deploy to that environment as well, respecting its branch. Both were stored and never read.
- An environment belonging to another repository can no longer be used to choose a deploy target.
- The deployment log names the preserved paths instead of printing raw rsync flags.