Repository navigation
chore: release 2.1.0, the CLI 1.5.0 and the extension 0.2.0 - #322
Merged
Merged
Conversation
The collection, at 2.1.0, gives each issue a stable code, and its notes open with the one change that breaks a reader of a result: getINPDetails() of INP returns a result object instead of an array. The CLI, at 1.5.0, ships those snippets, pairs the errors of --baseline by code and target, and gives the issue codes of each snippet in the schema resource of its MCP server. The extension, at 0.2.0, pairs the issues of two audits by code and target. package.json, cli/package.json, cli/server.json, extension/manifest.json, the lockfile, the examples of the JSON of the CLI and the version placeholder of the extension feedback form go to the new versions; both changelogs move Unreleased to their release, with links; the skills and llms.txt carry 2.1.0.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
Release of the stable issue codes (#316 to #321): the collection 2.1.0, the CLI 1.5.0 and the extension 0.2.0.
code, and atargetwhen there is one issue per thing, listed under Issue codes insnippets/SCHEMA.md. The notes open with the one change that breaks a reader of a result:getINPDetails()of INP returns a result object instead of an array (merged on 2026-10-16, in the CLI since 1.1.0), now first under Changed. It goes out as a minor version, as the CLI did.--baselinepairing the errors by code and target, and the issue codes of each snippet inwebperf://schema/{snippet}of the MCP server.codeandtarget.package.json,cli/package.json,cli/server.json,extension/manifest.jsonand the lockfile go to the new versions, and so do the examples of the JSON incli/README.mdandcontent/CLI.mdxand the placeholder of the extension feedback form. Both changelogs move Unreleased to the release, with their links. The skills andllms.txtcarry 2.1.0.After the merge: push
cli-v1.5.0right away, since the Copy prompt of the site pins the version ofcli/package.json, and approvenpm-publish; thenv2.1.0andextension-v0.2.0, which publish the release notes and the zip of the extension.Test plan
node scripts/check-tag-version.jswithv2.1.0,cli-v1.5.0andextension-v0.2.0(local): each matches its file;test:ci22 of 22.npm run smoke:cli-package(local): the packedwebperf-snippets-1.5.0.tgzinstalls in an empty folder; its MCP server lists 56 snippets, says how to install Chromium without it, and measures LCP after the install.npm run extension:zip(local) writeswebperf-snippets-extension-0.2.0.zip.auditworkflow on a page with five errors, measured with the published 1.4.0 as a baseline, without codes, against 1.5.0, with a code on each of the five: no new and no fixed errors, and the warning of another version of the CLI. The same with a baseline of 1.5.0: no new and no fixed errors.