Release yoastseo
and preview packages to NPM
#21410
Merged
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.
Important
Do not rebase this PR. The "Version increase" commit fa68e4c is the exact version that has been published to NPM. Orphaning this commit will make it impossible to properly determine changes since the published version.
Context
Summary
This PR can be summarized in the following changelog entry:
Relevant technical choices:
0.x.0-alpha.0
and the rest tox.0.0-alpha.0
@yoast/search-metadata-previews
and@yoast/social-metadata-previews
for now with all sub-dependenciesfiles
to determine what we would publish, see https://docs.npmjs.com/cli/v10/configuring-npm/package-json#files.map
files, in case the build contains them@yoast/browserslist-config
'sindex.js
out ofsrc
folder, for convenience of nosrc
in the published version (there's no build step that introduces abuild
folder)@yoast/replacement-variable-editor
Test instructions
Test instructions for the acceptance test before the PR gets merged
This PR can be acceptance tested by following these steps:
All changes in this PR are related to what we publish to NPM (which isn't used by any plugin). So this shouldn't effect the plugin itself at all. Any regression testing should be focused on JavaScript-powered features, and specifically those features provided by our NPM packages.
@yoast/components
look as before.Relevant test scenarios
Test instructions for QA when the code is in the RC
Impact check
This PR affects the following parts of the plugin, which may require extra testing:
UI changes
Other environments
[shopify-seo]
, added test instructions for Shopify and attached theShopify
label to this PR.Documentation
Quality assurance
Innovation
innovation
label.Fixes #