Update/wpcom reminder comment #65
Merged
Conversation
This file contains 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
* add test for videopress generated embed html * changelog Co-authored-by: Damián Suárez <rdsuarez@gmail.com>
* Prepare release 1.3.0 of Jetpack VideoPress standalone * Merge trunk and fix versions * correct versions * move versions back to 1.2.1
…#28432)" (Automattic#28447) This reverts commit 9439f40.
…tomattic#28436) Remove the error code `site_blacklisted` from the handler, as it's no longer being returned by WPCOM.
Co-authored-by: Renovate Bot <bot@renovateapp.com>
* Remove plugins/jetpack-mu-wpcom from the monorepo Will create jetpack-mu-wpcom as a package instead. * Update pnpm-lock
* Add initial jetpack-mu-wpcom package skeleton * Update gitignore and composer.json for WP tests * Add changelog
* Prepare release 1.3.0 of Jetpack VideoPress standalone * Add prerelease changelog
If the GH version tag has the "v" prefix, that should be stripped before comparing it with the SVN version and readme versions.
* Search: fix exceeding search limits in Jetpack Complete A site that has Jetpack Complete with exceeded Jetpack Search limits cannot use the instant search feature. We should not allow toggling the instant search option, the same way we don't allow it for Jetpack Search Free that is over limit. In the past, must_upgrade didn't check for the plan that blog has, but now it's safe to base the decision to disable instant search option only on that parameter. This commit introduces using `must_upgrade` to determine whether to disable instant search toggle. I've also added one final CTA that's shown to both Jetpack Search Free and Jetpack Complete users, shown once their search plan is disabled after three months of overages. Additionally, we will automatically disable instant search and search module on visiting Jetpack admin when `must_upgrade` is true (exceeded search limits). This shouldn't be needed most of the time, but occasionally the API call to disable it from overage cron might fail.
* Bundle image-guide into a single file * Make the bundle usable in boost * changelog * Update changelogs * Add a library name * Update library variable name * Update project versions
* propagate new vide data when replacing video * changelog * fix issue when picking guid from media item * fix setting attrs when uploading file * bump version
…ic#28241) GitHub has an unfortunate behavior in that workflow artifacts are not available via the API until the entire workflow has completed. This means that the "Test plugin upgrades" job in the build workflow unnecessarily delays the availability of the build artifact for Jetpack Live Branches and future wpcom automated testing for 6 or so minutes. To get around this, we create a new "Post-Build" workflow that is triggered by `workflow_run` after the Build workflow completes. But since this new workflow isn't automatically attached to the PR, we have to make API calls to get it to show up there. This is a second attempt at Automattic#25892, which had to be reverted as using the Actions app put the checks into the "suite" of a random workflow.
Something is not working right yet with the post-build job. Let's keep it around for debugging, but restore the copy in the build job so peoples' PRs aren't blocked by it.
* [not verified] handle files.URLs * [not verified] add tests for URL lib * [not verified] buildVideoPressURL() return empty object * change buildVideoPressURL() return value * changelog * escape . in the RegExp * escape the second dot 🤦
…block (Automattic#28474) * [not verified] remove the filter that prompts to conver embed * [not verified] changelog * [not verified] re-organize transforms code * [not verified] minor tidy * [not verified] clean up classes when transforming from Embed * [not verified] set explicitely attrs when transform to embed * [not verified] tweak to Embed transform
…ess video (Automattic#28477) * [not verified] improve fn to pick the GUID from URL * [not verified] do not transform when is not a videopress video * changelog
Co-authored-by: Brad Jorsch <anomiex@users.noreply.github.com>
* [not verified] try: enable Ads tab for Stats * [not verified] changelog * [not verified] Show Ads tab for Odyssey * [not verified] add wordads local controllers * [not verified] tweak wordads controllers * [not verified] changed supported version to 0.4.0-alpha * [not verified] fix up versions * [not verified] ignore WordPress.Security.NonceVerification.Recommended * [not verified] remove todo comment * [not verified] ignore unknow capatibility * [not verified] fix typo * [not verified] remove unecessary version test
…ic#28317) PT: pcmemI-1uJ-p2 Specific finding that led to this diff: pcmemI-1wa-p2#comment-1276 For simple sites, our new team page does not display viewers currently. This is because for simple sites, viewers are an entirely different implementation in a different table, and is normally accessed through a corresponding /sites/$site_id/viewers endpoint. Since it's clumsy on the frontend to call these two endpoints and combine data, we're introducing a new include_viewers argument to /sites/$site_id/users/ which when set to true: - only supports searching based on name for viewer - ignores order and order by parameters for the entire list and sorts by name This implementation should satisfy our current requirement while being entirely backwards compatible.
…mattic#28482) * tweak uploader component layout * changelog
* Add boost in My Plans * changelog * Fix yearly boost plan detection
* Changelog edits for 11.8-a.9 * changelog
* Install dependency for ProgressBar * Add get site size and policies APIs * Add actions, reducers and selectors for rewind details * Add BackupStorageSection component for Storage UI * Adjust admin layout to include BackupStorageSection * Fix review request component width * changelog * Move backup storage section on top for lower resolutions * Update backup package version to 1.11.0-alpha and composer.lock * UI improvements * Storage addon plugin API * Refactor add storage UI and add upsell prompt * Fix BackupStorageSpace returning 0 instead of not rendering * Adjust BackupStorageSpace grid positioning * Add a different section header when usage is critical * Make addon storage sizes more readable * Unit testing for storage addon upsell * Access class const property with `self` * Refactor, replacing `rewind` for `backup` * Remove unused import * Sort dependencies in alphabetical order Co-authored-by: Brad Jorsch <anomiex@users.noreply.github.com>
* Fix PHP warning when trying to delete inaccessible cache folder * Changelog Co-authored-by: Mark George <thingalon@gmail.com>
…omattic#28430) Co-authored-by: Jeremy Herve <jeremy@jeremy.hu>
* Update Form and variations icons * changelog * Icons adjustment
…c#28533) The composer output isn't printed anyway, let's save a bit of time in `check-intra-monorepo-deps.sh` and `fixup-project-versions.sh` by telling composer to not bother auditing the packages. Chances are renovate will let us know about any issues anyway.
…utomattic#28553) * expose videopress site settings to block editor * update site privacy label * changelog * remove exposed site settings in block editor * refactor privacy panel to use newly available video data
…es (Automattic#28545) * Fix scheduling events when none already scheduled * changelog * Refactor: declarative approach over event-driven approach Co-authored-by: Mark George <thingalon@gmail.com>
* Fix missing closing tag in http error description * changelog
…post edit (Automattic#28556) * Add a filter to allow users to control cache clearing after post edits * changelog Co-authored-by: Mark George <thingalon@gmail.com>
… `calypso_use_modernized_reading_settings` feature flag (Automattic#28549) Co-authored-by: Jeremy Herve <jeremy@jeremy.hu>
Store and track the usage of AI features so that we can later distinguish human-produced content from AI one.
* [not verified] first try * changelog * Some cleanup, add retry button * Some fix * Some re-work * More fixes * Refactor logic * Refactor logic * Add animated text * Fix issue when not enough characters are needed * Use closures for createPrompt * Rename state attributes that could be misleading * Make containsAiUntriggeredParapgraph more readable * Remove useless/wrong comment * [not verified] implement Brent's feedback * added useSelect dependencies * Some fixes * Small fixes * Better wording for ShowLittleByLittle state vars * Fix typo * Fix issue when switching order * Check length for the title * Added comment * Should display retry when the API errors * Save line breaks as <br/> * Remove isContentSet and use useEffect instead * Save animationDone in the component data to prevent redrawing issues where animation would not be triggered. * Use block name from index.js * Transform to <br/> on setting the content
…tes (Automattic#28566) * refactor video data check on video block attributes population * changelog
Release Jetpack AI to all WPCOM Users
…utomattic#28530) In various of our builds, postcss's autoprefixer is issuing the following warning ``` autoprefixer: start value has mixed support, consider using flex-start instead ``` According to [caniuse][1], of our supported browsers Safari does not recognize `start`. According to [the spec][2], `flex-start` is supposed to behave the same as `start` even if one of these winds up being used outside of a flex context. And the same for `flex-end` versus `end`. [1]: https://caniuse.com/mdn-css_properties_align-items_flex_context_start_end [2]: https://w3c.github.io/csswg-drafts/css-align/#positional-values
* Fix node 18 compatibility * Add changelog
This should make it easier to copy the command from the GitHub comment. See p1674724281751579-slack-CBG1CP4EN
|
Are you an Automattician? You can now test your Pull Request on WordPress.com. On your sandbox, run to get started. More details: p9dueE-5Nn-p2 |
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.
Fixes #
Proposed changes:
Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions: