Release JS Packages

[vraja-pro]

Important

Do not rebase this PR. The "Version increase" commit 1c35654 is the exact version of @yoast/ui-library and @yoast/tailwindcss-presetand the "version increase" commit dc8031e is the exact version of the other JS packages that have been published to NPM. Orphaning this commit will make it impossible to properly determine changes since the published version.

Context

• We want to release the following JS packages:
  • @yoast/replacement-variable-editor:2.0.0-alpha.3
  • @yoast/search-metadata-previews:3.0.0-alpha.2
  • @yoast/social-metadata-form:2.0.0-alpha.3
  • @yoast/social-metadata-previews:3.0.0-alpha.2
  • @yoast/ui-library:4.4.0
  • @yoast/tailwindcss-preset:2.5.0
  • @yoast/related-keyphrase-suggestions:0.3.0
  • @yoast/dashboard-frontend:0.2.0

Summary

This PR can be summarized in the following changelog entry:

• Releases new JavaScript package versions.

Relevant technical choices:

• The focus here was on releasing @yoast/ui-library

Test instructions

Test instructions for the acceptance test before the PR gets merged

This PR can be acceptance tested by following these steps:

• NA, just package releases, no code changes.

Relevant test scenarios

• Changes should be tested with the browser console open
• Changes should be tested on different posts/pages/taxonomies/custom post types/custom taxonomies
• Changes should be tested on different editors (Default Block/Gutenberg/Classic/Elementor/other)
• Changes should be tested on different browsers
• Changes should be tested on multisite

Test instructions for QA when the code is in the RC

• QA should use the same steps as above.

QA can test this PR by following these steps:

Impact check

This PR affects the following parts of the plugin, which may require extra testing:

Other environments

• This PR also affects Shopify. I have added a changelog entry starting with [shopify-seo], added test instructions for Shopify and attached the Shopify label to this PR.
• This PR also affects Yoast SEO for Google Docs. I have added a changelog entry starting with [yoast-doc-extension], added test instructions for Yoast SEO for Google Docs and attached the Google Docs Add-on label to this PR.

Documentation

• I have written documentation for this change. For example, comments in the Relevant technical choices, comments in the code, documentation on Confluence / shared Google Drive / Yoast developer portal, or other.

Quality assurance

• I have tested this code to the best of my abilities.
• During testing, I had activated all plugins that Yoast SEO provides integrations for.
• I have added unit tests to verify the code works as intended.
• If any part of the code is behind a feature flag, my test instructions also cover cases where the feature flag is switched off.
• I have written this PR in accordance with my team's definition of done.
• I have checked that the base branch is correctly set.
• I have run grunt build:images and commited the results, if my PR introduces new images or SVGs.

Innovation

• No innovation project is applicable for this PR.
• This PR falls under an innovation project. I have attached the innovation label.
• I have added my hours to the WBSO document.

Fixes #

[coveralls]

Pull Request Test Coverage Report for Build 330d209319251933e61442cd7cd1d2189806b681

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 53.315%

---

Totals
Change from base Build 9bd05739bcb156d9caf636bbe410044fe5f1f585:	0.0%
Covered Lines:	32856
Relevant Lines:	61810

---

💛 - Coveralls

[FAMarfuaty]

LGTM