DevOps Release Checklists
Repeatable, browser-only validation gates before you ship. Each checklist composes existing tools on this site into a named workflow you can copy as Markdown into a PR, ticket, or Slack.
Pre-release
API Release Checklist
Validate the OpenAPI spec, scan sample responses for secrets and PII, check security headers, confirm sign-off.
Open checklist →OpenAPI Breaking Change Checker
Walk through every common breaking-change category before bumping your spec version.
Open checklist →Local Kubernetes YAML Validator
Parse the YAML, scan env blocks for secrets, confirm probes, limits, and service-account hygiene.
Open checklist →Dockerfile Review Checklist
Lint locally, scan for baked-in secrets, confirm pinned base, non-root user, and multi-stage build.
Open checklist →Secrets & PII Pre-check
Scan diffs and sample logs for secrets and PII before merge or external sharing.
Open checklist →JWT Security Checklist
Decode a token, confirm alg, exp, iss, aud, and scan the auth config for accidentally committed keys.
Open checklist →Migration & support
Environment Variable Comparison
Compare env files side-by-side and confirm secret hygiene before promoting config.
Open checklist →CSV Reconciliation for Migration
Compare source vs. target rows, confirm encoding and date formats before cutover.
Open checklist →Private HAR Sanitizer for Support
Strip cookies, auth headers, tokens, and PII before sharing a HAR with support or a vendor.
Open checklist →How these work
Each checklist is a static page. Some items run a quick local check (the page calls an existing tool's headless adapter in your browser). Others link out to a full tool for hands-on inspection. The rest are manual confirmations with optional notes. When you finish, copy the report as Markdown.
Related
- Workflow Gallery — multi-step workflows that chain tools together.
- All tools — the individual utilities each checklist composes.
Choosing the right checklist
Start with the artifact that creates the biggest release risk. API teams usually begin with the API Release Checklist, then run the OpenAPI compatibility review if clients depend on the schema. Platform teams often start with Kubernetes or Dockerfile checks before comparing environment variables.
What a good checklist result includes
- A short summary of what changed and which environment was checked.
- Links or pasted evidence from local tools, with secrets and personal data removed.
- Clear owner, reviewer, and rollback notes for anything risky.
Private by default
These checklists run as static browser pages. When a checklist opens a scanner or parser, the input is processed locally in your browser and can be copied into your own PR or ticket system only when you choose to do that.