Recued
Menu
← Back to recipes

Records runtime compatibility canary

by recued-core v1 10 views

Use “Records runtime” in Recued. It helps you complete this workflow using the connections and settings you choose.

Complete workflow

Use Inbound Artifact Verification in Recued for signature, checksum, minisign, and integrity. It includes 8 built-in actions and 3 ready-to-run workflows. Actions that change data use Recued's approval controls.

You are viewing one recipe in this workflow. Installing it opens the complete pack so its other recipes and background automations arrive together.

Use “Register an inbound artifact” in Recued. Record a file you have received so it can be verified. Keyed on its path, so re-registering the same file converges on the same row instead of creating a second one.

pack:inbound-artifact-verificationverificationrecordsv2
by recued-core pinned v2

Use “Verify an inbound artifact” in Recued. Run every applicable check against a file on disk — version fingerprint against the sender's published checksum, a detached Minisign signature against a public key you already hold, archive integrity, and a member listing — and record each result separately.

pack:inbound-artifact-verificationverificationsignaturechecksum
by recued-core pinned v2

Use “Show artifact verifications” in Recued. List received artifacts with each check's result shown separately. It reads information without changing data in the connected service.

pack:inbound-artifact-verificationverificationboardrecords
by recued-core pinned v2
View pack details, dependencies, and permissions →
How it works 1 step

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (1 steps)
require_runtime ?

About

Details

1 steps recipe_id: inbound-artifact-verification-require-records-runtime