Specify a composer autoloader-suffix such that the Composer class names don't change each deploy. #411
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Due to how composer works, it generates a new autoloader classname on each build, this is generated from a hash of the built configuration - which includes the git hash of the latest git commit to this repo.
This results in changes such as this, without any meaningful changes to the actual composer autoloaders:
As there should only ever be a singular instance of
wporg-mu-plugins
loaded, we can instead specify a static suffix:This shouldn't cause any compat issues, and will reduce the changes in build diffs, and avoid situations where the new Class is loaded but the old classname is called, which can happen in a race-condition during WordPress.org deploys.