v0.6.6

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Features

• scdev cleanup now prunes only truly unused resources - previously the bare command deleted every volume of the current project, and --global deleted volumes across every registered project plus orphans, contradicting how "cleanup" is normally understood (cf. docker system prune, npm cache clean) and making the command unsafe to run without thinking. The --global flag is gone; scdev cleanup now lists and removes (in one combined confirm): (1) state entries whose project directory is missing from disk, (2) containers carrying the scdev.project label whose project is no longer registered + on disk, (3) volumes not owned by any still-registered project. Orphaned containers are removed before volumes so the old "volume is in use" failure - which hit projects whose state was dropped but whose containers stayed alive - no longer blocks the volume pass. Resources belonging to still-registered projects are never touched; use scdev remove for a full project tear-down.

v0.6.5

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Features

• Transparent forwarding of colon-namespaced subcommands via scdev <cmd> - when a justfile declares a recipe literally named after the file (e.g. console *args: in console.just), scdev now invokes just as just -f console.just console <args...> so arguments containing colons (cache:clear, db:migrate, dal:refresh:index) flow through as recipe parameters instead of being parsed as just's module-path separator. Template authors can now wrap CLIs like bin/console or artisan with a single catch-all recipe - scdev console cache:clear forwards straight to bin/console cache:clear inside the container. Without a filename-matching recipe, behavior is unchanged (first arg is the recipe name), so existing templates keep working.

v0.6.4

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Bug Fixes

• Fix scdev exec printing Error: exit status N on non-zero shell exit - when an interactive shell started via scdev exec <service> sh exited with a non-zero code (Ctrl+D on some shells returns 130, a failed command inside the shell returns its own code), cobra wrapped the child's exit in Error: exit status N and the scdev process itself exited with 1, losing the original exit code. Ctrl+D out of an exec'd shell now returns cleanly to the host shell with no error output, and any non-zero child exit code is propagated verbatim instead of being squashed to 1. Matches how docker exec and standard shells behave.

v0.6.3

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Bug Fixes

• Fix auto-update rate-limit death spiral on shared IPs - when the GitHub API call failed (rate limit, 5xx, transient network error), refreshAndInstall returned without writing ~/.scdev/update-check.json, so the next invocation retried immediately instead of waiting the 24h TTL. On a shared egress IP (office NAT, VPN, CI pool) once any user hit GitHub's 60-req/hour unauthenticated limit, every retrying user kept burning credits faster than the window refilled, starving everyone else's next-day refresh. The cache is now always written on error with LastChecked bumped and prev ETag/LatestTag/InstalledTag preserved, so a failed attempt counts as "checked recently."

v0.6.2

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Bug Fixes

• Fix auto-update never running on fast commands - the background update check was launched as an unjoined goroutine, so Go's runtime killed it when main() returned. Fast commands like scdev version, scdev list, and scdev status finish before the GitHub API round-trip completes, so ~/.scdev/update-check.json was never written and auto-update effectively never ran. Made the refresh synchronous: API probe bounded to 3s, download/install bounded to 60s. Cache-hit path (99% of invocations) is unchanged at ~6ms; stale-cache path now blocks for ~200ms on a 304 or ~1-2s when a new release is actually being downloaded. Cost is paid at most once per 24h per machine.

v0.6.1

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Features

• scdev open command - opens the current project's URL in the default browser. scdev open uses the project in the working directory; scdev open <name> looks up any registered project by name. Protocol follows the global SSL setting (http/https). Closes the common "I need the URL again, let me run scdev info and copy-paste" loop.

v0.6.0

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Features

• Background auto-update with banner - scdev checks for updates in the background (at most once per 24h, conditional GET with ETag) and, if the running binary is in the symlink layout, silently downloads the new release into ~/.scdev/bin/scdev. No sudo, no re-exec. The next invocation prints a one-line banner informing you that you've been upgraded. Legacy installs (plain binary in /usr/local/bin/) still get a "run scdev self-update to migrate" banner. Opt out with SCDEV_NO_UPDATE_CHECK=1; CI environments are detected automatically.
• Checksum-verified installs and updates - every path that downloads an scdev binary (install.sh, scdev self-update, the background auto-update) now fetches checksums.txt alongside the binary and verifies SHA256 before chmod-ing it executable. A compromised release asset or HTTPS MITM via a rogue CA can no longer silently run code on your machine. Releases without checksums.txt (pre-0.6) are rejected rather than falling back to unchecked install.

Bug Fixes

• Fix stale shared-service containers silently breaking after config changes - if a shared service (Mail, DB UI, Redis Insights, Router) was created while SSL was off and SSL later got flipped on (or image, domain, or dashboard settings changed), scdev services start would just start the stale container instead of recreating it, so the new Traefik labels never took effect. Symptoms: https://db.shared.<domain> redirecting to the docs page, HTTPS URLs for other shared services falling through to the 404 catch-all. Shared services now carry the same scdev.config-hash label that project services use; startService compares it to the hash of the freshly built expected config on every call and recreates the container on drift. The router keeps its "don't recreate just to shrink ports" behavior (other projects' ports would be dropped) via a union-of-ports check before hashing.
• Fix lost updates to the state file - every mutating operation on the state manager (RegisterProject, CreateLink, AddLinkMembers, RenameProject, etc.) used to Load then Save as two independent locked calls, so a concurrent goroutine (like the background update-check doing its own work in parallel with scdev start) could interleave and clobber changes. Operations now hold the manager's lock for the entire read-modify-write cycle via a new Mutate(fn) helper. Cross-process concurrency (two scdev invocations at once on the same state file) is still unprotected - documented, not a regression.
• Fix scdev self-update hanging indefinitely on slow GitHub responses - the GitHub API call and binary download now use a 5-minute context timeout, matching what the background update-check was already doing. Previously a stalled GitHub response meant the user had to Ctrl-C.

Improvements

• Remove unused config fields - shared.tunnel and shared.observability were defined in config but never wired to any service manager; enabling them did nothing except (for observability) print an observe.shared.<domain> URL in scdev info that 404'd. pre_start was in ServiceConfig and documented in the README but no code ever executed the listed commands. All three are gone. Re-implementation tracked as SC-127, SC-128, SC-146.
• Remove phantom persist_on_delete help text - scdev down -v and scdev remove -v flag help advertised "respects persist_on_delete" but no such field exists anywhere in config or code. Removed the claim; if anyone wants the feature for real it's tracked as SC-147.
• Smaller, safer cmd/* bootstrap - new withProject(timeout, fn) / withDocker(timeout, fn) helpers in cmd/shared.go collapse the timeout + Docker-availability + project-load boilerplate that every runXxx repeated. Roughly 150 lines of duplication gone across 15+ commands.
• Single shared-service registry - shared service metadata (name, subdomain, container name, start/stop/status/connect/disconnect funcs, per-project opt-in flag) now lives in one place: services.AllSharedServices(). Adding a new shared service is a single-file change instead of updating two hand-rolled registries (cmd/services.go and internal/project/shared_services.go) plus hoping they stay in sync.
• Other small cleanups - strings.Join/strconv.Itoa for the router's port CSV label, html.EscapeString replaces a hand-written HTML escaper on the docs page, shared teardownContainers helper between Project.Down and Project.Rename, and cleaner early-return control flow in NetworkDisconnect.

v0.5.6

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Improvements

• scdev step styling refinement - the whole header line is now bold cyan (not just the ▶), and a trailing blank line separates the header from the command output that follows. Each phase reads as a framed section, not a single colored glyph next to white text.

v0.5.5

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Features

• scdev step <message> subcommand - prints a visually distinct progress marker (two leading blank lines, cyan ▶, bold text) for use inside .scdev/commands/*.just recipes. During scdev setup, top-level status messages like "Installing PHP extensions" previously got buried in the wall of apk/composer/npm output; @scdev step "..." replaces @echo for phase headers so they pop against the noise. Auto-plain on non-TTY, NO_COLOR, or global plain mode. scdev start's own "Starting project ..." line now uses the same helper.

Improvements

• Template authoring docs updated - templates/README.md, skills/scdev/references/templates.md, and the scdev skill now recommend @scdev step for setup.just phase headers and explain why, with the base/Nuxt/Symfony examples rewritten to use it.

v0.5.4

Update

scdev self-update

Install

macOS / Linux:

curl -fsSL https://raw.githubusercontent.com/ScaleCommerce-DEV/scdev/main/install.sh | sh

---

Bug Fixes

• Fix scdev update ignoring env/image/volume/command changes - serviceNeedsRecreate only compared Traefik labels and bailed out with "Project is up to date" on any other change, leaving stale containers running. It now compares a deterministic scdev.config-hash label stamped on each container, covering image, env, volumes, command, working dir, routing, published ports, and network aliases. Containers created before the label existed are recreated once on first update after upgrade.

Improvements

• Skill updates for template creation and existing-project setup - expanded skills/scdev/ references (new stack-gotchas reference, richer config examples and template authoring notes, updated SKILL.md with rename/link commands and per-service routing.domain guidance) to help agents scaffold new templates and onboard scdev into existing projects.
• README and template docs: Symfony/Sylius/Laravel trusted-proxies troubleshooting - documented the mixed-content / stuck debug toolbar / broken admin login failure mode caused by Traefik terminating HTTPS without a trusted-proxy env var, plus PHP template authoring tips (memory_limit drop-in, install-php-extensions, asset-pipeline builds).