shippinglisted

# Shipping and Launch Ship with confidence: deploy safely, with monitoring in place, a rollback plan ready, and a clear definition of success. Every launch should be reversible, observable, and incremental. Faster is safer — smaller batches and more frequent releases reduce risk, not increase it. ## When to use - Deploying a feature or significant change to production for the first time. - Migrating data or infrastructure. - Opening a beta or early access program. - Any deployment that carries risk (all of them). **Not for:** setting up CI/CD pipelines (use `ci-cd`); routine commits, branching, or conflict resolution (use `git-workflow`); rolling back a live failure (use `debugging` first, then ship the fix). ## Steps ### 1. Complete the pre-launch checklist Before deploying, every section must be green. **Code quality** - [ ] All tests pass (unit, integration, e2e) - [ ] Build succeeds; lint and type checking pass - [ ] Code reviewed and approved - [ ] No `console.log` / debug statements; no pre-launch TODOs left - [ ] Error handling covers expected failure modes **Security** - [ ] No secrets in code or version control - [ ] Dependency audit (`npm audit`, `pip-audit`, `cargo audit`, ...) shows no critical/high vulnerabilities - [ ] Input validation on all user-facing endpoints - [ ] Authn/authz in place; rate limiting on auth endpoints - [ ] Security headers (CSP, HSTS); CORS scoped to specific origins, not wildcard **Performance & accessibility** — adapt to your s