Shipping

17 documents

A/B testing

Pre-ship A/B test verification: ensure experiment variants are configured, defaults are safe, and the debug panel override works.

Bulk operation verification

After any operation touching 5+ files, run a verification pass for stale references before marking complete.

Continuous delivery

Keep main always releasable via an automated build-test-deploy pipeline; releasing is a business decision, not a manual scramble.

Database backup and recovery

Pre-deployment backup verification: ensure backups run before migrations, WAL files are handled during restore, and integrity checks pass before shipping.

sqlitepostgresql

Dependency Security

Your dependencies are your attack surface. Manage them actively.

pythontypescript

Ephemeral preview environments

Provision a disposable per-PR environment from IaC, seed it with throwaway data, test against it, and auto-destroy on merge or close.

Feature flags

Pre-ship feature flag verification: ensure all new features are gated, defaults are correct, and flag keys are documented.

csharpkotlinswifttypescript

Incident response and blameless postmortems

Run production incidents with defined command roles and severity tiers, then close them with blameless, tracked-to-completion postmortems.

MSIX Packaging

- Use the single-project MSIX packaging model

windows

Progressive delivery

Decouple deploy from release and limit blast radius with canary, rings, blue-green, flags, and health-based automated rollback.

Schema evolution and migrations

Pre-deploy migration verification: ensure version tracking, idempotency, sync compatibility, and rollback strategy before shipping schema changes.

sqlitepostgresql

Ship a privacy manifest and declare required-reason APIs

Ship a PrivacyInfo.xcprivacy manifest declaring data collection and required-reason API usage, or App Store submission is rejected.

iosmacosswift

Small, atomic commits

One logical change per commit. A change may touch multiple files if they are part of the same concept. Commits should...

Software supply-chain integrity

Emit an SBOM and signed SLSA provenance per build, then verify both signatures and provenance at deploy time.

Transport Security

Pre-deploy transport security verification: TLS 1.2+, HSTS enabled, cipher suites audited, certificate pinning validated.

typescriptweb

Trunk-based development

Integrate to one shared trunk in small daily increments behind feature flags, keeping trunk releasable instead of trading rigor for long branches.

Windows ARM64 and Native AOT

Ship native ARM64 builds for Windows on ARM; adopt Native AOT and trimming only when a measured need justifies their constraints.

windowscsharp