Bulk Plugin Management: Disable auto updating plugins when page loads

[vykes-mac]

Related to https://github.com/Automattic/dotcom-forge/issues/9706

Proposed Changes

Currently when the list of plugins are fetched those that have autoupdate enabled immediately execute the update on page loads, we want to disable this behaviour.

• Disable auto update when page loads

Why are these changes being made?

• Improve performance and product quality

Testing Instructions

• Ensure some of your plugins have autoupdate enabled
• Go to /plugins/manage
• Verify auto update is not executed by checking no update api calls were made

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[matticbot]

This PR modifies the release build for the following Calypso Apps:

For info about this notification, see here: PCYsg-OT6-p2

• notifications
• odyssey-stats
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/remove-autoupdate-when-plugins-fetched on your sandbox.

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-124076

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-124076&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-124076&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~551 bytes removed 📉 [gzipped])

name                             parsed_size           gzip_size
stats                                 -182 B  (-0.0%)      -62 B  (-0.0%)
site-marketing                        -182 B  (-0.0%)      -67 B  (-0.0%)
settings-discussion                   -182 B  (-0.0%)      -64 B  (-0.1%)
plugins                               -182 B  (-0.0%)      -56 B  (-0.0%)
plans                                 -182 B  (-0.0%)      -59 B  (-0.0%)
marketplace                           -182 B  (-0.0%)      -56 B  (-0.0%)
marketing                             -182 B  (-0.0%)      -60 B  (-0.0%)
jetpack-social                        -182 B  (-0.0%)      -60 B  (-0.0%)
jetpack-cloud-plugin-management       -182 B  (-0.0%)      -56 B  (-0.0%)
home                                  -182 B  (-0.0%)      -59 B  (-0.0%)
email                                 -182 B  (-0.0%)      -59 B  (-0.0%)
checkout                              -182 B  (-0.0%)      -61 B  (-0.0%)
activity                              -182 B  (-0.0%)      -63 B  (-0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Async-loaded Components (~56 bytes removed 📉 [gzipped])

name                          parsed_size           gzip_size
async-load-design-playground       -182 B  (-0.0%)      -56 B  (-0.0%)
async-load-design                  -182 B  (-0.0%)      -56 B  (-0.0%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[paulopmt1]

Removing this sounds good to me. As we talked on Slack, can we also double-check how the current auto-update mechanism looks like? So we can proper document that in the Project Thread.

[paulopmt1]

@vykes-mac I removed the label so it won't appear duplicated in the project items list since we're already tracking it using this issue. This will help me when creating tomorrow's summary.