Repository navigation
Rebuild WordPress on PHP updates with fresh parents - #17
Merged
Merged
Conversation
dbpolito
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Receive the existing docker-php-updated event after PHP parent publication. Rely on the PHP parent scheduled rebuild and dispatch rather than a redundant WordPress cron. Keep push, pull request, manual, and repository-dispatch triggers.
Pull every parent stage in test and publish builds, serialize releases without cancelling publication, and exercise pull requests without exposing publishing credentials. Remove the temporary single-architecture push before multi-architecture publication.
Add template consistency validation and update obsolete action runtimes so the workflow can run on current hosted runners. Keep the current image matrix; document the retained PHP 8.1 tags as unmaintained upstream rather than implying rebuilds patch that parent.
A local fresh-parent amd64 8.4-nginx build reports PHP 8.4.27; executable/config checks passed. The existing CLI bootstrap check exits zero with HTTP-context warnings. Multi-architecture publication and end-to-end dispatch delivery were not exercised; no images were published.