Repository navigation
Signed builds from the release action and upload are now also made
strict-ready, ready for devices running a client release with strict mode
(API 1.2). No released client supports strict mode yet, so nothing changes on
your devices today. Devices in signed mode take the build as before.
What happens in a signed job
After the upload, the action runs the
SimpleOTA CLI on the runner. It
signs the build number SimpleOTA assigned, together with the project, the key
and the image's SHA-256, and attaches that strict signature to the build. The
key is used on the runner and only the signature is sent to SimpleOTA.
The step summary shows the result: signed, strict-ready or
signed, not strict-ready.
Best effort
Making a build strict-ready never fails the job. If it does not work, for
example because the CLI cannot be downloaded or the server has no
strict-signature endpoint, the upload and any deployment go ahead and the job
succeeds with a warning in this form:
::warning::<reason> Build <build> was uploaded but is not strict-ready. Finish with: simpleota build make-strict <build> <bin>
<reason> says what went wrong, for example Could not install the SimpleOTA CLI. or The strict signature was not attached.
Until a build is made strict-ready, SimpleOTA does not offer it to devices in
strict mode.
The pinned CLI
This release pins
SimpleOTA CLI 0.2.0
and the SHA-256 of its Linux and macOS archives (amd64 and arm64) in
scripts/cli-pin.txt. Signed jobs download it into RUNNER_TEMP and refuse it
if the checksum differs, so pinning the action pins the code that handles your
key. The download runs without your token or key in its environment.
- A
simpleotaalready on the runner's PATH is used instead of downloading. - The new
cli-versioninput, on the release action andupload, names
another CLI release. That release is checked only against its own published
checksums, not ones pinned here.
Unsigned builds install nothing.
Also changed
- The step summary prints the rollout percentage as a number, so
rollout-percentage: 050reads50%. - The README and links point at
wassie-devinstead ofxanderwasserman.
Upgrading
No workflow change is needed, and no existing input or output changed.
deploy and promote are unchanged. v1 points here. Pin @v1.1.0 if you
pin exactly.
Full Changelog: v1.0.3...v1.1.0