Skip to content

chore: release 2.1.0, the CLI 1.5.0 and the extension 0.2.0 - #322

Merged
nucliweb merged 1 commit into
mainfrom
chore/release-2.1.0
Oct 25, 2026
Merged

nucliweb merged 1 commit into
mainfrom
chore/release-2.1.0

Conversation

@nucliweb

Copy link
Copy Markdown
Owner

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.

  • Collection 2.1.0: every issue has a code, and a target when there is one issue per thing, listed under Issue codes in snippets/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.
  • CLI 1.5.0: the snippets with their codes, --baseline pairing the errors by code and target, and the issue codes of each snippet in webperf://schema/{snippet} of the MCP server.
  • Extension 0.2.0: the audit comparison pairs issues by code and target, lists a change of severity as a change, and the downloaded report carries code and target.

package.json, cli/package.json, cli/server.json, extension/manifest.json and the lockfile go to the new versions, and so do the examples of the JSON in cli/README.md and content/CLI.mdx and the placeholder of the extension feedback form. Both changelogs move Unreleased to the release, with their links. The skills and llms.txt carry 2.1.0.

After the merge: push cli-v1.5.0 right away, since the Copy prompt of the site pins the version of cli/package.json, and approve npm-publish; then v2.1.0 and extension-v0.2.0, which publish the release notes and the zip of the extension.

Test plan

  • node scripts/check-tag-version.js with v2.1.0, cli-v1.5.0 and extension-v0.2.0 (local): each matches its file; test:ci 22 of 22.
  • Lint and CLI unit 329 of 329 (local); the suites of feat(snippets): give the issues of the CSS, font and image snippets of Loading a stable code, and require one #321 ran on the same code.
  • npm run smoke:cli-package (local): the packed webperf-snippets-1.5.0.tgz installs 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) writes webperf-snippets-extension-0.2.0.zip.
  • By hand with the packed package (local): the audit workflow 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.
  • The extension by hand: an audit saved with 0.1.1 compared with one of 0.2.0 on the same page.

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.
@vercel

vercel Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
webperf-snippets Ready Ready Preview Oct 25, 2026 12:56pm UTC

@nucliweb
nucliweb merged commit 973d423 into main Oct 25, 2026
3 checks passed
@nucliweb
nucliweb deleted the chore/release-2.1.0 branch October 25, 2026 14:44

This branch was successfully deployed

1 active deployment
Preview — e0cae083 Deployed Oct 25, 2026 by vercel[bot]
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.

1 participant