replit-upgrade-migration

# Replit Upgrade & Migration ## Current State !`cat .replit 2>/dev/null | head -15 || echo 'No .replit found'` !`cat replit.nix 2>/dev/null || echo 'No replit.nix found'` ## Overview Guide for upgrading Replit environments: Nix channel updates, package version bumps, database migrations (KV to PostgreSQL, dev to prod), deployment type changes, and Node.js/Python runtime upgrades. ## Prerequisites - Existing Replit App with `.replit` and `replit.nix` - Git version control (recommended) - Backup of critical data before migration ## Instructions ### Step 1: Upgrade Nix Channel Nix channels determine available package versions. Upgrade to get newer runtimes. ```toml # .replit — before [nix] channel = "stable-23_05" # .replit — after (2024-2025 stable) [nix] channel = "stable-24_05" ``` After changing the channel, reload the shell (exit Shell tab and re-enter). Then verify: ```bash node --version # Should show newer version python3 --version # Should show newer version ``` ### Step 2: Upgrade Node.js or Python Runtime ```nix # replit.nix — update runtime packages # Before (Node 18) { pkgs }: { deps = [ pkgs.nodejs-18_x pkgs.nodePackages.typescript ]; } # After (Node 20) { pkgs }: { deps = [ pkgs.nodejs-20_x pkgs.nodePackages.typescript-language-server pkgs.nodePackages.pnpm ]; } ``` ```toml # .replit — update modules to match modules = ["nodejs-20:v8-20230920-bd784b9"] ``` **Verify after upgrade:** ```bash node --version # v20....