v0.2.0

uses: github.com/mozership/probe-jmap@52000030f1bd839677830d1ab07a024183f581b7 # v0.2.0

Highlights

• Its action.yml declares guard: [read-only, allow-host], so Probe v1.21.0 or later runs it under --read-only and --allow-host without --allow-action.
• Its action.yml declares params, so probe check reports a key of with the action does not take.
• A key of with the action does not take now fails the step.

Declaring the guard

The action already refused, before anything was sent, a method that may write under --read-only, and a host --allow-host does not allow, for the session, the API URL and each redirect. Probe could not tell, so it still refused the step unless --allow-action named the action. action.yml now declares both kinds, and Probe v1.21.0 or later runs the action under them.

Parameters

params: [url, calls, using, account_id, basic_auth, headers, timeout] in action.yml lets probe check report a misspelled key with its line. The action checks the same list itself, so a key that is not one of them fails the step before anything is sent; it used to be ignored.

Requirements

The action needs Probe v1.21.0 or later, which reads what action.yml declares. Its e2e runs on Probe v1.21.0 against Stalwart. See JMAP.

Changelog

• e65bfa6 Declare the guard the action keeps to and the params it takes
• 2d237fe Link to Probe where it is now, mozership/probe
• 7ec02df Merge pull request #2 from mozership/link-mozership-probe
• 7bb65b1 Merge pull request #3 from mozership/declare-guard-and-params
• 295701f Point action.yml at v0.1.0