Repository navigation
v1.22.0
Highlights
- The built-in
browserandmail-latencyactions are now external actions, mozership/probe-browser and mozership/probe-mail-latency. A workflow that uses either has to name it by repository and commit. mail-latencynow runs under--allow-hostwithout--allow-action.- The docs pin graphql and jmap at v0.2.0, which keep to
--read-onlyand--allow-hostand declare the keys ofwiththey take. - Probe no longer depends on chromedp.
- For library users: the packages of the two actions moved to their repositories.
browser and mail-latency are external actions
The two actions left Probe for repositories of their own, with the same with and the same result. A step names each one by repository and commit in place of the built-in name:
# Before
- uses: browser
- uses: mail-latency
# After
- uses: github.com/mozership/probe-browser@42dda412d5d183c091f8baf071237cc090f16052 # v0.1.0
- uses: github.com/mozership/probe-mail-latency@2340503ddb7081e1a7e4cc7e4391ac6e5937574d # v0.1.0uses: browseranduses: mail-latencyare now unknown actions, andprobe checkreports them.- Probe downloads each executable the first time a workflow uses it, and checks it against the SHA-256 in the
action.ymlat the pinned commit. Each release's notes start with theusesline to copy. - Their
action.ymldeclaresparams, soprobe checkreports a key ofwiththe action does not take. - browser declares no guard, as it cannot tell what a page will do: under
--read-onlyor--allow-host, it still needs--allow-action. mail-latency declaresallow-host, as it connects to no host, so it now runs under--allow-hostwithout--allow-action. It writes its CSV, so it does not declareread-only. - The built-in actions are now
http,db,grpc,shell,ssh,smtp,imap,embeddedandhello.
See Browser and Mail Latency.
graphql and jmap v0.2.0
The docs, the example and the e2e pin the external actions at v0.2.0:
uses: github.com/mozership/probe-graphql@41e4ffa222db58c63c7169117c919e6d252bdbf9 # v0.2.0
uses: github.com/mozership/probe-jmap@52000030f1bd839677830d1ab07a024183f581b7 # v0.2.0- Both declare
guard: [read-only, allow-host], so they run under a guard without--allow-action. graphql keeps to it from this release: under--read-onlyit sends only a query, read with a GraphQL parser, and under--allow-hostit checks the host ofurland of each redirect. - Both declare
params, and fail a step whosewithhas a key they do not take.
For library users
The packages moved with the actions, with no alias left:
| Before | After |
|---|---|
github.com/linyows/probe/actions/browser |
github.com/mozership/probe-browser/browser |
github.com/linyows/probe/actions/mail-latency (package maillatency) |
github.com/mozership/probe-mail-latency/maillatency |
actions.Names, actions.Params and actions.AllParams no longer list browser or mail-latency, and a module importing probe no longer pulls in chromedp. See CHANGELOG.md.
Changelog
- ce65807 Date v1.22.0 the day it is released
- 768748b Merge pull request #354 from mozership/chore/external-actions-v0.2.0
- a06e99f Merge pull request #355 from mozership/feat/browser-external
- f5f328f Merge pull request #356 from mozership/feat/mail-latency-external
- fcb3d89 Merge pull request #357 from mozership/release/v1.22.0
- 93165b1 Move the browser action out of Probe, to mozership/probe-browser
- 8fa551a Move the mail-latency action out of Probe, to mozership/probe-mail-latency
- 610cb5e Pin probe-graphql and probe-jmap v0.2.0, which declare the guard they keep
- 1ef7454 Prepare the changelog for v1.22.0