Update/dataviews package

[BogdanUngureanu]

This version doesn't contain any changes since the last release. I'm bumping it just to be on the latest version.

Proposed Changes

• Update the dataviews package with upstream changes.

Why are these changes being made?

• Keeping in sync with upstream

Testing Instructions

• There are no upstream changes since the last version

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 UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• 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)?

[github-actions]

Calypso Live (direct link)

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

Jetpack Cloud live (direct link)

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

Automattic for Agencies live (direct link)

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

[matticbot]

This PR does not affect the size of JS and CSS bundles shipped to the user's browser.

Generated by performance advisor bot at iscalypsofastyet.com.

[BogdanUngureanu]

Hey @oandregal do I need to bump version of automattic/dataviews package in this PR or do I need to create a separate PR for it?

From what I understand from the FG post, that should be done in a separate PR, right?

Imo, since this version doesn't bring any code updates. should we skip the automattic/dataviews release?

[oandregal]

@BogdanUngureanu thanks for taking care of this!

I'm at the end of my day, and I'd like to review this one before merging (make sure the commit hashes are proper, etc.) with a fresh brain, as it's the first that is done by someone else :) Thank you so much 🙏

I see we're in a similar timezone, so do you mind if I review this first thing in my morning, and we proceed with merging then?

From what I understand from the FG post, that should be done in a separate PR, right?

Yeah, no need to create a new @automattic/dataviews version — that's only done when we are about to release the npm package and that's a separate process.

[matticbot]

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

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

• help-center
• notifications
• wpcom-block-editor

To test WordPress.com changes, run install-plugin.sh $pluginSlug update/dataviews-package on your sandbox.

[oandregal]

Also! This PR is not merged via the UI, it needs to be done via the CLI (sync doc).

[BogdanUngureanu]

Thanks @oandregal, no rush! :)

Also! This PR is not merged via the UI, it needs to be done via the CLI (sync doc).

yep, I noticed that, thanks for the reminder. :)

[oandregal]

I did the process myself and checked that the two commits coming from Gutenberg have the same hashes that in this PR: b0e92f5 and f12ffd3. The subtree split docs promised this, but it's the only tool that did, so I thought I'd double-check before proceeding.

If you'd bear with me, I'd like to do a little experiment: I'm going to mark this PR as "request changes". Please, proceed with merging via the CLI when you're ready.

I'd like to understand if there's anything that would prevent these PRs from being merged via UI but let them be merged via CLI. If you're able to push, like I think you would, I'd like to prepare a follow-up PR to add a check in TeamCity that just fails for PRs that update the CHANGELOG.md (we only update this for PRs that sync from upstream).

[oandregal]

I'd like to prepare a follow-up PR to add a check in TeamCity that just fails for PRs that update the CHANGELOG.md (we only update this for PRs that sync from upstream).

Prepared a PR for this at #103296