Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement infrastructure for launching standalone plugins from modules, including WebP Uploads #699

Merged
merged 125 commits into from
Apr 5, 2023

Conversation

felixarntz
Copy link
Member

@felixarntz felixarntz commented Apr 5, 2023

Summary

This brings almost all Milestone 1 changes from #656 into the trunk branch, at first to publish only the WebP Uploads standalone plugin, as a first test. Once that is published, we will quickly follow up with the remaining standalone plugins (see #640).

This PR doesn't need an actual code review, just 2 approvals as a formality. All code in this branch has already been reviewed and approved in previous PRs.

Checklist

  • PR has either [Focus] or Infrastructure label.
  • PR has a [Type] label.
  • PR has a milestone or the no milestone label.

mukeshpanchal27 and others added 30 commits March 2, 2023 17:49
…-plugins

CLI command for a build process to transform modules into standalone plugins
…Press/performance into feature/creating-standalone-plugins
@felixarntz felixarntz added [Type] Enhancement A suggestion for improvement of an existing feature Infrastructure Issues for the overall performance plugin infrastructure Creating standalone plugins labels Apr 5, 2023
@felixarntz felixarntz added this to the 2.2.0 milestone Apr 5, 2023
Copy link
Member

@joemcgill joemcgill left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It looks like everything that we need to create the standalone plugin for WebP Uploads is here. We will want to do a dry run of the manual workflow prior to running a real release. Given that we can only do that once this is committed to trunk, let's merge this, and create a follow-up issue to handle the final steps that need to be fixed before we run an actual release.

@felixarntz
Copy link
Member Author

Thanks @joemcgill, I've opened #700 for this purpose.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Infrastructure Issues for the overall performance plugin infrastructure [Type] Enhancement A suggestion for improvement of an existing feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants