Skip to content

1.1.0

Latest

Choose a tag to compare

@SixFive7 SixFive7 released this 23 Sep 11:50
· 162 commits to master since this release

A web page can offer its own tools to the browser. From this version they can be called. A name invented by a page is still refused at the door; the page's tool is reached through one tool of ours, and that tool is judged like every other.

The rest is upkeep and repair. Velopack moved for the first time since this project started. The installer is a 64-bit program now, and Windows will show the app's size in Add/Remove Programs, where it showed nothing. One note told a caller its cookies had survived a crash. The measurement says they may not have, and the note says that now.

Added

  • ✨ A web page's own tools are callable, through one tool of ours that is judged like the rest. read more
  • ✅ The scratch configuration the suite hands the real client is seeded as already onboarded. read more
  • ✅ A log event id must be unique in its class, and the scan found a second collision on its first run. read more

Changed

  • 🐛 Two client-liveness events shared event id 76, so both moved off it and the id is retired. read more
  • 📦 Every release packs full packages only, so an update downloads the whole thing. read more
  • 🔧 The relaunch note stops promising that stored state survived, because it may not have. read more
  • ⬆️ Velopack rolled 1.2.0 to 1.2.158, and the Windows installer is a 64-bit bootstrapper now. read more
  • 📝 A browser server that ends itself loses the same stores as one that is killed. read more
  • 📝 The feed is asked once per server start, and a hundred browsers in one session ask nothing. read more
  • 🔧 webmcp: true is written into every generated config rather than left to upstream's default. read more
  • 📝 Dash style for the whole repository is recorded as an open question rather than settled. read more
  • 📝 Three decisions about page-provided tools, with the directions not taken beside them. read more
  • 🔧 A session's deletion, what a destroy takes, its upload root and its move are all said now. read more
  • ✅ Four arms hold the session-lifetime rules on the published binary's own wire. read more
  • 💥 The payload could not be rebuilt until the override's exit was adjudicated. read more
  • 📝 The charter's version-chain example prints the chain that ships, and an arm holds it there. read more
  • 📝 The README licensing tables name Firefox, the third Playwright package, and today's revision. read more
  • 📝 The session ledger is snapshotted again, and a re-snapshot is not an edit. read more
  • 🗑️ The idle-CPU axis is retired as not established, and the other three are unchanged. read more
  • 📝 The third-party notices name the third Playwright package and both browsers we provision. read more
  • 📦 The release manifest records the pulled-forward dependency, and copies the file that pins it. read more
  • 📝 Resume is two paths now, and each was timed at 1245 and 1548. read more
  • 📝 The cost ratios are re-taken at 1245 and 1548, and the idle-CPU axis is withdrawn. read more
  • 📝 Four claims in the payload licensing row did not survive a re-read at 1245 and 1548. read more
  • 📝 Disk after a first run is a measured number again: 598 MB. read more
  • ⬆️ TUnit moved 1.68.4 -> 1.68.17 and this time the testing platform moved with it, 2.4.0 -> 2.4.1. read more
  • ⬆️ The payload rolled to @playwright/mcp 0.0.82, and three browser revisions came with it. read more
  • 🗑️ The dated playwright-core override is removed, four days after it was taken. read more
  • ✅ The exit test, its positive control and the version ordering underneath them are retired. read more
  • 🔒 A web page can add tools to the child's tools/list, and BrowserAI's surface does not move. read more
  • 🔧 Two tools left the surface and nobody here judged them out. read more
  • 📝 Four re-verification rows are marked [STALE] and owed, and the reason is on each. read more
  • 📝 The session ledger is snapshotted for the last time, and the scratch folder is empty. read more

Icon Meaning Icon Meaning
✨ new capability 🐛 fix
🔧 behaviour or configuration change 🔒 security or permissions
🗑️ removal or deprecation 💥 breaking, or the reader must act
📝 documentation ✅ tests and the gate
📦 packaging, installer, release pipeline ⚡ performance
♻️ refactor with no behaviour change ⬆️ dependency move

The full changelog for this release: CHANGELOG.md