chore(release): 1.6.0 - #23
Merged
Merged
Conversation
TWD Contract Validation
23 passed · 41 failed · 3 warnings · 1 skipped Failed validations./contracts/users-3.0.json
./contracts/posts-3.1.json
./contracts/products-3.0.json
./contracts/events-3.1.json
|
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.
Version bump for the layout snapshot support merged in #21, plus the failure diagnostics from #20 and the puppeteer bump from #19.
Replaces #22, which had this staged as a prerelease.
What is in it
--update-snapshotsand--cidrivetwd.matchLayoutheadlessly, and a run writes a self-contained.twd/snapshot-report.htmlwith every failure capture embedded, so CI needs one artifact rather than a zip of loose PNGs.npm audit.Read this before merging
The viewport change is not opt-in.
page.setViewport()now runs on every run, not just when recording, so a run that never touches a layout snapshot still moves from Puppeteer's implicit size to1280x800. A test that happened to depend on the old size can behave differently.viewportintwd.config.jsonpins your own.This is the one way 1.6.0 differs from 1.5.0 in kind. Sharding could promise "no behaviour change without
--shard". This release cannot make that promise, and the CHANGELOG says so in those words rather than burying it.The snapshot flags need
twd-js1.10.0, which is not published yet. On an older version there is nomatchLayoutto drive and the flags do nothing. That is stated in the CHANGELOG. It does not block this release, but it does mean the snapshot half of 1.6.0 stays inert untiltwd-jsships.Process
Per
CLAUDE.md:package.jsonto1.6.0package-lock.jsonregenerated withnpm run lock:linux, so the version moved in both places it lives and the lock is the Linux one CI consumesconventional-changelogis not used here479 tests passing.
Release title
Stable, so the title is exactly the tag: