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

Update FSE plugin to version 1.11.0 #43857

Merged
merged 3 commits into from
Jul 2, 2020
Merged

Conversation

andrewserong
Copy link
Member

@andrewserong andrewserong commented Jul 2, 2020

This PR bumps the FSE plugin version to v1.11.0 for rolling out another release. It includes a fair few changes based on looking at https://github.com/Automattic/wp-calypso/commits/master/apps/full-site-editing. I've cross-referenced these below:

Included changes:

Testing instructions

  • Sandbox the diff associated with this version bump (D45821-code)
  • Test on a simple site
  • Test on an Atomic site with the Gutenberg plugin enabled
  • Test on an Atomic site without the Gutenberg plugin
  • Test in Calypso and via wp-admin

If approving this PR, please approve D45821-code, too :)

@Automattic/serenity can you please double-check that the commits included in this release are working correctly? I'm not so familiar with the Donations or Premium Content blocks, so just want to make sure it's all good to go!

@matticbot
Copy link
Contributor

@andrewserong andrewserong requested review from a team July 2, 2020 05:56
@andrewserong andrewserong added the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Jul 2, 2020
@matticbot
Copy link
Contributor

Caution: This PR affects files in the FSE Plugin on WordPress.com
Please ensure your changes work on WordPress.com before merging.

D45821-code has been created so you can easily test it on your sandbox. See this FieldGuide page about developing in the FSE Plugin for more info: PCYsg-ly5-p2

@matticbot
Copy link
Contributor

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.

@simison simison requested a review from akirk July 2, 2020 06:21
@akirk
Copy link
Member

akirk commented Jul 2, 2020

Unfortunately this doesn't include #43792 which I just have merged now. Could you do another run and update? Thanks!

Copy link
Contributor

@jeyip jeyip left a comment

Choose a reason for hiding this comment

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

✅ Works on simple sites
✅ Works on atomic sites
✅ Works on atomic site without the Gutenberg plugin
✅ Works on Calypso and wp-admin for all the mentioned sites

@andrewserong
Copy link
Member Author

Thanks @akirk — I'll rebase and include it!

@andrewserong
Copy link
Member Author

The change in #43792 to update the text domains for the newspack blocks doesn't seem to be working properly in the CI build. I've commented more fully over in that PR: #43792 (comment)

@andrewserong
Copy link
Member Author

@akirk has resolved the issue with the text-domains by adding the step to install composer in the FSE build process. This ensures that #43792 will work correctly in CI.

Copy link
Member

@mmtr mmtr left a comment

Choose a reason for hiding this comment

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

@Automattic/serenity can you please double-check that the commits included in this release are working correctly? I'm not so familiar with the Donations or Premium Content blocks, so just want to make sure it's all good to go!

All good from our side!

- name: Run composer
uses: nick-zh/composer-php@master
with:
action: 'install'
Copy link
Member

Choose a reason for hiding this comment

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

Are Composer packages cached in Circle CI?

Copy link
Member

Choose a reason for hiding this comment

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

Could you elaborate on that question? We're using Github Actions here, no?

Copy link
Member

Choose a reason for hiding this comment

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

🤦 hah, of course no circle ci here.

So e.g. node_modules gets cached so that running yarn is faster, and I was wondering if results from composer install also could get cached?

Copy link
Member

Choose a reason for hiding this comment

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

Ah I am by no means an expert in this realm. All I can say that the time added by the composer install was really minimal, so I am not sure if it's worth trying to cache something.

Copy link
Member

Choose a reason for hiding this comment

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

Screenshot 2020-07-02 at 11 22 16

Copy link
Member

Choose a reason for hiding this comment

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

Sounds good then! :-) 👍 Thanks for checking the time.

@Addison-Stavlo Addison-Stavlo merged commit ee86659 into master Jul 2, 2020
@Addison-Stavlo Addison-Stavlo deleted the update/fse-plugin-to-v-1-11 branch July 2, 2020 15:01
@matticbot matticbot removed the [Status] Needs Review The PR is ready for review. This also triggers e2e canary tests and wp-desktop tests automatically. label Jul 2, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants