Skip to content

chore: release 2.2.0, the CLI 1.6.0 and the extension 0.3.0 - #337

Merged
nucliweb merged 1 commit into
mainfrom
chore/release-2.2.0
Oct 26, 2026
Merged

nucliweb merged 1 commit into
mainfrom
chore/release-2.2.0

Conversation

@nucliweb

@nucliweb nucliweb commented Oct 26, 2026 •

Copy link
Copy Markdown
Owner

Summary

Release of the result labels (#328 to #336) and the budgets of the CLI (#325, #326): the collection 2.2.0, the CLI 1.6.0 and the extension 0.3.0.

  • Collection 2.2.0: two changes break a reader of a result, both first under Changed: the recommendations of Cache-Strategy-Analysis carry no emoji, so their priority is their order, and INP, Interactions and Input-Latency-Breakdown return tracking instead of error before any interaction. The results read with labels and units from the shared view of snippets/_view/, in the extension and in the visualizer of the site.
  • CLI 1.6.0: a budget for every metric it measures (FCP, TTFB and INP join LCP and CLS), every budget with its verdict in every report, and a budget that was not measured no longer passes, which changes the exit code of such a run (first under Changed). The human and markdown reports read the details of a result with the labels and units of the extension.
  • Extension 0.3.0: results with labels and units, phases as a chart, tables that fit the panel, issues that lead to their row, Open in Sources and Copy URL, the recommendations, and the audit table filtered by severity.

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 and an opening paragraph on what breaks. The skills and llms.txt carry 2.2.0.

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

Test plan

  • node scripts/check-tag-version.js with v2.2.0, cli-v1.6.0 and extension-v0.3.0 (local): each matches its file; test:ci 22 of 22.
  • Lint, CLI unit 354 of 354 and generate-skills:check (local).
  • npm run smoke:cli-package (local): the packed webperf-snippets-1.6.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.3.0.zip.
  • By hand with the package packed as publish-cli.yml packs it, with snippets/ and so snippets/_view/ (local): the audit workflow on audit-violations.html, measured with the published 1.5.0 as a baseline, against 1.6.0: the warning of another version of the CLI and no new or fixed errors. The same with a baseline of 1.6.0: no new or fixed errors. The human report shows the labels of the view (Selector html>body>img · Lazy type loading-lazy).
  • The extension 0.3.0 by hand, loaded unpacked.

@vercel

vercel Bot commented Oct 26, 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 26, 2026 9:17pm UTC

@nucliweb
nucliweb merged commit a4d5153 into main Oct 26, 2026
3 checks passed
@nucliweb
nucliweb deleted the chore/release-2.2.0 branch October 26, 2026 21:28

This branch was successfully deployed

1 active deployment
Preview — 31cf4e6c Deployed Oct 26, 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