ReleaseCompletion
Corex\Config\Releases\ReleaseCompletion · class · Config layer
The end of an installation, done by the release that was just put in place (spec 107, US3; plan D8 and D19; FR-030, FR-032, FR-035). The files are the new release’s. This brings the database to it, and only then says the release is installed: records it as the site’s, lets visitors in, removes what the installation unpacked and the package it came in, and writes it down. It asks for no key. The key opens WordPress’s maintenance answer, which this request has already passed or which has ended by itself. So an installation whose browser went away is finished by whoever next opens the Releases screen and may install releases. What it writes down says how this request got in (ReleaseMaintenance::keyCameFrom()): through the gate, and with the key from where, or after maintenance had ended.
Public API
Section titled “Public API”__construct(ReleaseStore $store, ReleaseFinisher $finisher, InstalledRelease $installed, ReleaseStaging $staging, ReleaseSafeguards $safeguards, ReleaseJournal $journal, ReleaseRecord $record)
Section titled “__construct(ReleaseStore $store, ReleaseFinisher $finisher, InstalledRelease $installed, ReleaseStaging $staging, ReleaseSafeguards $safeguards, ReleaseJournal $journal, ReleaseRecord $record)”finish(int $actorId, DateTimeImmutable $now): array
Section titled “finish(int $actorId, DateTimeImmutable $now): array”Do the database step, or the next part of it on a network, and finish when it is done.