What I build outside work, most of it with CI on every change and an automated release. Each card says how it ships, and the code is on GitHub.
How it ships: Python tools with a pytest suite that builds a sample workspace end to end. Runs on my own machine as a scheduled task.
How it ships: CI checks the frontend (lint, types, tests) and the Rust side (fmt, clippy, tests). A version tag builds macOS and Windows binaries into a draft GitHub release.
How it ships: Nothing ships yet. The capstone will deploy through Argo CD.
How it ships: CI on every pull request: type checks, lint, tests and npm audit. A merge to main deploys the proxy to Vercel from GitHub Actions and smoke-tests it; a version tag builds the Android app on EAS.
How it ships: When the version on main changes, GitHub Actions runs the tests, publishes to npm with provenance, then tags the release. CodeQL scans the code.

How it ships: CI runs lint, types, unit and database tests, checks the migrations match the schema, then runs Playwright end-to-end tests. Vercel migrates the matching Neon branch before each build: production for main, a shared dev branch for previews.

How it ships: CI on every pull request: lint, types, tests and a build. Vercel deploys a preview per branch and production from main.

How it ships: Vercel deploys a preview per branch and production from main.

How it ships: release-please opens the release PRs. A release builds Android, iOS, macOS, Windows and web, each file with a signed build-provenance attestation. Main deploys the web app to GitHub Pages once the tests and an integration run pass.

How it ships: Published to the VS Code Marketplace.

How it ships: Published to the VS Code Marketplace.