v0.1.0

uses: github.com/mozership/probe-browser@42dda412d5d183c091f8baf071237cc090f16052 # v0.1.0

Highlights

• The first release of the browser action as an action of its own. It was the built-in browser action of Probe up to v1.21.0, and Probe v1.22.0 no longer has it.
• The same with and the same result: a step changes only its uses, from browser to the line above.
• Its action.yml declares params, so probe check reports a key of with the action does not take. It declares no guard.

From the built-in action

# Before, with Probe v1.21.0 or earlier
- uses: browser

# After
- uses: github.com/mozership/probe-browser@42dda412d5d183c091f8baf071237cc090f16052 # v0.1.0

• The action drives a real Chrome through chromedp, which has to be installed where Probe runs, as before.
• It cannot tell what a page will do, so it declares no guard: under --read-only or --allow-host, a step that uses it is refused unless --allow-action names it, as the built-in action was.
• It needs Probe v1.21.0 or later.
• Its e2e runs it through Probe v1.21.0 in Chrome against a fixture page: reading the page, a full-page screenshot, and the page saved when an action fails.

See Browser.

For library users

The package moved here: github.com/linyows/probe/actions/browser is now github.com/mozership/probe-browser/browser, with the same API.

Changelog

• 22d0454 Drive a browser from a Probe workflow, as an action of its own