ReleaseRecord
Corex\Config\Releases\ReleaseRecord · class · Config layer
What happened to a site’s release, written down twice (spec 107, US5; FR-051; plan D14). In the installer’s own log, which is a file beside the releases: it has to hold when a release’s database change failed and the tables are in doubt. And in the activity log, where an administrator looks for who did what, when it can take an entry. An installation’s key is given to neither. What reaches this is versions, a reason and a package’s name.
Public API
Section titled “Public API”__construct(ReleaseStore $store, ActivityService $activity, Closure $nameOf, ?Closure $signedInWith)
Section titled “__construct(ReleaseStore $store, ActivityService $activity, Closure $nameOf, ?Closure $signedInWith)”entries(): array
Section titled “entries(): array”What happened here, newest first, each with the name of who did it.