maintaining-lt-stacklisted

Single source of truth for stack-wide maintenance and releases of the lt base repos ("Grund-Repos"): the dependency graph (nuxt-extensions to nuxt-base-starter, nest-server to nest-server-starter), the release recipe per repo including both marketplaces, npm propagation waits, the HTTPS push fallback for an empty SSH agent, and the smoke test as release gate. Activates on "maintain stack", "release all repos", "stack release", "Grund-Repos aktualisieren", and behind /lt-dev:publish. NOT for a single npm package (use maintaining-npm-packages). NOT for nest-server upgrades inside customer projects (use nest-server-updating).
lenneTech/claude-code · ★ 0 · AI & Automation · score 72

Install: claude install-skill lenneTech/claude-code

# Maintaining the lt Stack (all base repos) The seven base repos are maintained and released in dependency order. Canonical source is [github.com/lenneTech](https://github.com/lenneTech); releasing needs a local clone of each, and that checkout path differs per machine — locate it instead of assuming one: ```bash find "$HOME" -maxdepth 5 -type d -name nest-server-starter -not -path '*/node_modules/*' 2>/dev/null ``` If a repo is not checked out anywhere, clone it into the same workspace directory as its siblings. Target end state: every repo current, `check` green everywhere, npm packages published, templates tagged — proven by a full `/lt-dev:fullstack:smoke-test` run. ## Dependency graph (dictates the order) ``` Wave 1 (parallelizable): nuxt-extensions nest-server lt-monorepo cli │ │ ▼ (wait for npm publish!) Wave 2 (parallelizable): nuxt-base-starter nest-server-starter │ ▼ Validation: /lt-dev:fullstack:smoke-test (exercises ALL repos live) │ ▼ Wave 3 (only on findings): patch fixes → re-release affected repos ``` **Rule:** A starter is only updated once its npm package actually resolves on npm (`npm view <pkg> version` == new version), not when the GitHub release exists — the publish.yml action takes minutes. ## Running the waves