Test and release
Know exactly what changed before you ship.
Compare the new version with the last reviewed one, run the right checks, and save every result with the exact app and action version.
A clear release decision
See what changed and whether it is ready to move forward.
Deploy compares one new version with the last reviewed version. It puts important changes first while keeping the full history available.
The next step stays simple: finish the missing checks, hold the release, or move this exact version forward.
Everything needed to review a release
Save the decision with the version it applies to.
A locked version
A release candidate that cannot quietly change after review.
What changed
A direct comparison with the last reviewed version, including anything removed, broken, or not yet checked.
Tests to run
The app build, focused tests, safety checks, and real Siri or Shortcuts checks needed for this release.
Proof from the release
Every result linked to the exact action, app build, device, tool version, and time.
Exact versions, exact changes
Compare the new version with the last one someone reviewed.
The same action ID connects the two versions. Deploy shows what changed, disappeared, broke, or still needs checking instead of burying the decision in a large data table.
Checks that match the change
Move forward only after the required checks pass.
One green check is not enough. Deploy keeps the product review, code tests, app build, and real Siri or Shortcuts check separate. It also records when a feature is intentionally unsupported.
Review the action
Confirm the inputs, results, changes, errors, permissions, confirmation, owner, and where the action should appear.
ReviewedBuild the exact candidate
Compile the named app target and settings with the new connection calling the app’s existing code.
PassedRun focused tests
Cover the normal path, app-data searches, errors, safety checks, cancellation, and saving where the action needs them.
Awaiting resultTry the installed feature
Use the exact build in Shortcuts or Siri on a named device. A planned automated test is not presented as a result that already exists.
Manual checkDifferent checks answer different questions
Do not reduce five checks to one “supported” badge.
Reading code, running tests, building the app, trying the real feature, and seeing live use are different kinds of proof. Keep each result separate.
The action definition and the app code it calls were inspected
Focused feature and bug-check results
The exact app target and settings compiled
Shortcuts and Siri on a named build and device
Records from real use and product results
A clear release record
Know exactly which version each result belongs to.
Each result names the action and release under review, plus the app version, build, tool version, device, time, result, and source needed to understand it later.
One action from start to finish
Keep the same action through every step.
Audit finds the task. Build defines it. Preview shows where it should appear. Deploy tests one exact release. Measure records what happened when that version ran.
Plan one well-tested release
Ship what you can prove.
Bring one reviewed app action. Leave with an exact comparison, a release decision, a test list, and a plan for saving the results.