-
Notifications
You must be signed in to change notification settings - Fork 846
Update paid-newsletters with trunk #28171
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
Conversation
* Show regenerate notice only if Critical CSS module is active * changelog
* Add package image-guide * [not verified] Attempt to use the image-guide package * changelog * Specify a main file in package.json * Two step build * Use simpler type syntax since prettier... doesn't like it? * Build image-guide on boost e2e tests * changelog * Setup tests * Attempt to fix imports * Change main file * Fixed monorepo package dependencies * changelog * Update package.lock * Update boost pnpm packages * Attempt to fix monorepo package version refs * changelog * Another attempt to fix failed checks * changelog * Update boost packages * Revert main in package.json * Change main file * Fix type imports * [not verified] Revert "Fix type imports" This reverts commit 66c2ead. * Allow heart-of-team to approve PRs for image-guide js package * Specify main and types files separately * Import types differently Co-authored-by: Mark George <[email protected]>
…ity (#26417) Co-authored-by: brent <[email protected]> Co-authored-by: Fabien MILLERAND <[email protected]> Co-authored-by: Brent Nef <[email protected]> Co-authored-by: Romario <[email protected]> Co-authored-by: Matías Ventura <[email protected]> Co-authored-by: Matias Ventura <[email protected]> Co-authored-by: MILLER/F <[email protected]> Co-authored-by: Kuba Birecki <[email protected]> Co-authored-by: Jeremy Herve <[email protected]> Co-authored-by: Brandon Kraft <[email protected]>
Co-authored-by: Mark George <[email protected]>
…27987) Co-authored-by: Candy Tsai <[email protected]>
* [not verified] Fix the out-of-bounds menu. It also caused the menu to flicker if you positioned the mouse in a specific position * [not verified] Add the listener in the init funciton * [not verified] Fix the arrow display * [not verified] Fix missing spaces and changelog text * [not verified] Prevent code from running twice * [not verified] Add explanation for using a fallback for the viewport check * [not verified] Remove the focus when leave the main element * [not verified] Use the link height instead of hardcoding it * [not verified] Checking if the site is atomic through a global variable instead of using a class to do it Co-authored-by: Valter Lorran <[email protected]>
* Adjust Form placeholder footer links style * changelog
Co-authored-by: Jeremy Herve <[email protected]>
* [not verified] Allow supporting merge PRs with changelogger. * [not verified] Add changelog. * [not verified] Update version number for CLI. * [not verified] Upgrade changelogger reference in all plugins. * [not verified] Add changelogs. * [not verified] Also add support for default merge message from GH. * [not verified] Add unit test for supporting merge in changelogger. * [not verified] Remove unneeded capturing groups and added anchoring. * [not verified] Apply coding standards. * [not verified] Remove redundant test.
* [not verified] add jetpack_videopress shortcode * [not verified] move width and height out of poster data * [not verified] add generated jetpack_videopress shortcode to video details component * [not verified] changelog * [not verified] specify the video block * [not verified] improve shortcode markup * [not verified] read guid as first unnamed argument * change shortcode to videopress and override jetpack shortcode * [not verified] change generated shortcode * changelog * fix video url on block by id * fix versions * simplify existing shortcode check * add cover attribute
) Co-authored-by: Derek Smart <[email protected]>
If a block is unsupported in the mobile app, a user can still edit it via a web view (known as the "Unsupported Block Editor" or "UBE"). Since the introduction of the blogging/writing prompts on WordPress.com, the block no longer loads within the UBE. The prompts display instead. This PR fixes that issue by preventing the prompts from displaying if it's detected that the editor is loading from the mobile app.
* my-jetpack: fix Product card layout issue * fix product card detail layout issue * fix VideoPress seach layout issue * fix VideoPress detail input layout issue * changelog * fix VideoPress clipboard button layout issue * bump My Jetpack version
* Add copy-webpack-plugin dep * changelog * re-organize building blocks folders * copy block.json files when building * point to buld when registering blocks * fix file paths in video block def * fix file paths Video Chapters block def * exclude src/client files in prod * Copy extensions index file JSON file to the build directory * Reference correct extensions index JSON file * use Assets lib to regiters extensions * refactor extensions. Add helpers. * move copy-webpack-plugin to dev deps * load scritps to handle extendd blocks * debug() unregistering core/embed videopress * update deps Co-authored-by: Luiz Kowalski <[email protected]>
* Update Form child blocks icons * changelog
* Payment blocks: Fix upgrade nudge in the site editor. * Pass only "ref" from blockProps
* remove unused editor.js file * changelog
Co-authored-by: Derek Smart <[email protected]>
* Initial placement of review prompt in post publish panel * Add ability to dismiss review prompt * Update the permission check function name * changelog * Update conditions for showing the review prompt * Fix project versions * Add analytics to review prompt * Swap out typed URL * Conditionally load the connection state * Updates based on feedback, performance improvements * Fix connection package JS error * move analytics functionality into an existing hook, fix logic error * changelog * Refine conditions for when the review request should show * Allow review prompt to be disabled via filter, add check for post already shared * Change method for checking whether post is already shared * changelog * Fix meta default for already shared * version management
* Add the image-guide to exclusions from the Jetpack and packages list * Mark it as non-private for npm publishing * Remove eslint file, to let the standard monorepo rules in the door * changelog * Clean up linting complaints Co-authored-by: Mark George <[email protected]>
* Do not allow analytics errors to break other things * changelog Co-authored-by: Mark George <[email protected]>
* Track image-guide ui toggle * Track image guide images and page Signed-off-by: Adnan Haque <[email protected]> * Add initial state and page impact tracking to image guide Signed-off-by: Adnan Haque <[email protected]> * changelog * Fix build issues Signed-off-by: Adnan Haque <[email protected]>
|
Are you an Automattician? You can now test your Pull Request on WordPress.com. On your sandbox, run |
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. 🔴 Action required: Please add missing changelog entries for the following projects: Use the Jetpack CLI tool to generate changelog entries by running the following command: Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped. Beta plugin:
Jetpack plugin:
Debug Helper plugin:
Backup plugin:
Vaultpress plugin:
Boost plugin:
Search plugin:
Social plugin:
Starter Plugin plugin:
Protect plugin:
Videopress plugin:
Super Cache plugin:
Jetpack Mu wpcom plugin:
|
This reverts commit 4a84d2a.
Fixes #
Changes proposed in this Pull Request:
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions: