Skip to content

Releases

LaunchStack CLI v3.0.6

Choose a tag to compare

@github-actions github-actions released this 15 Nov 10:21
46d9d9b

LaunchStack CLI 3.0.6

LaunchStack CLI 3.0.6 improves concurrent project mutations, production auditing and runtime feedback. It also documents generated Docker builds that need a custom certificate authority.

Fixes and improvements

  • Capability mutations now replan while holding the project lock. Concurrent independent installs are serialized against the latest manifest and state, keeping their generated files and metadata together.
  • Production audit checks base and production Compose configuration together, so required CORS and JWT settings inherited from the base file do not produce false findings.
  • Audit distinguishes a project outside a Git repository from actual path enumeration failures and resource bounds. The non-Git notice explains that tracked-file secret checks could not run and how to include them.
  • Commands on unsupported Node.js versions now stop with an actionable message. --help and --version remain available. Supported versions are Node.js 24.22.0+ and 26.13.0+ within their respective major lines.
  • The Docker guide shows how to provide a custom CA to generated production builds through a BuildKit secret without adding it to the image.

Verification

The v3.0.5 package was installed from npm and exercised through project creation, validation, capability installation, client and resource generation, reconciliation, upgrade planning, dependency installation, generated-project checks, PostgreSQL-backed authentication flows and production Docker health/readiness checks. Database tests passed 26/26; generated project checks passed 24 tests with 2 database tests skipped in the separate no-database workspace. The custom CA was provided to BuildKit as a secret for the Docker build.

The local v3.0.6 release gate passed on Node.js 24.22.1 with PostgreSQL 16. Formatting, lint, strict typechecking, 44 root test files / 198 tests, the 1,290-case security corpus, reproducible distribution build, package inspection, production dependency audit (zero vulnerabilities), 23-component SBOM validation, packed CLI smoke and generated-project smoke all passed. Generated API checks passed 9 test files / 28 tests, Prisma 6.19.3 generation, database schema sync, TypeScript build and production dependency audit. The production Docker image passed health and PostgreSQL readiness checks with the custom CA passed to BuildKit as a secret. Runtime checks printed the version on Node.js 24.22.3 and 26.13.1, allowed help/version on Node.js 20.18.0, and returned the documented compatibility error for a Node.js 20 command.

The capability mutation benchmark measured one transaction installing 1, 10 and 100 synthetic file-only capabilities at 20.518 ms, 20.921 ms and 96.562 ms p50. General transaction runs at 100, 1,000 and 10,000 files measured 110.175 ms, 727.163 ms and 6.062 s p50. The 10,000-file p95 was 6.277 s. Workloads, machine details and limitations are in the benchmark documentation.

Install

npm install --global launchstack-cli@3.0.6
launchstack --version

See the README, compatibility guide, Docker guide and release history for usage and supported runtimes.

LaunchStack CLI v3.0.5

Choose a tag to compare

@github-actions github-actions released this 15 Nov 08:16
655b034

LaunchStack CLI 3.0.5

LaunchStack CLI 3.0.5 is a hotfix release focused on project mutation reliability and day-to-day CLI behavior.

Fixes and improvements

  • Project mutations use an atomic directory lock, avoiding hard-link requirements on FUSE, network and restricted filesystems. Stale-owner detection and concurrent writer serialization remain in place. An empty or incomplete lock initialization is never reclaimed by age alone; if its process crashed before writing verifiable owner metadata, verify that no mutation is running, remove .launchstack/mutation.lock, and retry.
  • Existing lock files from older CLI releases remain compatible while live. If one is stale, the CLI asks the user to verify no mutation is running and remove that legacy lock; new directory locks recover stale owners automatically.
  • launchstack validate reads and validates v3 launchstack.json project manifests and retains support for legacy launchstack.config.json files.
  • launchstack create <name> --directory <parent> now creates <parent>/<name>. Add --verbose to see the generation stages.
  • The declared runtime floor is Node.js 24.22.0 or later in the 24.x line, or Node.js 26.13.0 or later in the 26.x line. CI and Docker continue to use current patched Node.js 24 and 26 releases.
  • Capability documentation distinguishes complete local wiring for Redis, queue and cron from helper-only OAuth, storage, observability, WebSocket, email and webhook support.

Verification

npm run release:check passed on Node.js 24.22.1 and Node.js 26.13.1, each with PostgreSQL 17. Both runs passed formatting, lint, typecheck, 43 test files / 186 tests, the 1,290-case security corpus, reproducible distribution build, package inspection, production dependency audit (zero vulnerabilities), 23-component SBOM validation, packed CLI smoke and generated-project smoke. Each generated API check passed 9 test files / 28 tests, Prisma 6.19.3 generation, TypeScript build and production dependency audit. Node.js 26.13.1 ran in an Alpine container.

npm run docker:template:smoke passed: the generated production image passed its healthcheck and PostgreSQL readiness probe. The transaction benchmark ran three isolated samples each at 100, 1,000 and 10,000 files; p50 was 82.7 ms, 546.5 ms and 5.12 s, with 6.19 s p95 at 10,000 files. The full measurements, memory samples and methodology are in docs/benchmarks/transactions.md. This Node.js 24.22.1 run is not directly comparable with v3.0.4's separate host sample. CI remains configured for both supported Node.js lines.

Runtime and installation

npm install --global launchstack-cli@3.0.5
launchstack --version

See the README, compatibility guide, capability guide and release process for command usage and supported runtimes.

LaunchStack CLI v3.0.4

Choose a tag to compare

@wbizmo wbizmo released this 14 Nov 18:14
c457eb9

LaunchStack CLI 3.0.4

Released: 2026-11-14

Verified changes

  • Establishes supported Node.js 24.22.3 and 26.13.1 patch baselines, based on the Node.js release index dated 2026-11-10. Node 20 support is removed. This is a breaking runtime support change and is not semver-compatible with a patch release; it is recorded explicitly for review.
  • Moves root and generated API container builds to Node 24.22.3. Generated API CI tests Node 24.22.3 and 26.13.1.
  • Requires explicit CORS origins and JWT secrets in production Compose configuration.
  • Copies the generated healthcheck script into the generated production image.
  • Upgrades Zod to 4.6.7 to address the high severity advisory affecting versions below 4.6.6.
  • Pins production Node images by digest and carries the generated healthcheck script into the nonroot runtime image.
  • Keeps Prisma at 6.19.3, the latest Prisma 6 release. Prisma 7's new client and datasource configuration need a separately tested migration to preserve current generated-project compatibility.
  • Rejects malformed recovery journals before touching project or external paths, protects the secret store from symlinks and permissive POSIX modes, and gives new projects unique development JWT secrets.
  • Binds generated local services to loopback and expands audit checks for runtime policies, lockfiles and production Compose settings. launchstack audit --advisories adds npm registry evidence for production dependencies and reports LS024 when the check cannot complete.
  • Marks secret-looking tracked filenames as heuristic findings, bounds Git path enumeration to 16 MiB / 10 seconds and emits LS022 when enumeration is incomplete. LS005 does not inspect file contents. The measured 1k–100k audit results are in docs/benchmarks/security-audit.md.
  • Rejects non-public IP addresses across all remote OpenAPI DNS answers and pins HTTPS connections to the validated answers to prevent DNS rebinding.
  • Serializes stale transaction-lock reclamation by lock inode and treats unreadable Linux process identity as unverifiable/live. Cross-platform absolute path forms are rejected consistently.
  • Replaces the root Docker image with a non-root Node 24 CLI image that invokes dist/cli.js; the Docker smoke checks both the CLI image and generated API production health/readiness.
  • Adds bounded deterministic security corpus checks under a 128 MiB V8 heap and 15 second timeout. The recorded 1,290-case run is in docs/benchmarks/security-fuzz.md; it is not coverage-guided fuzzing.
  • Documents that generated API rate limiting uses an in-memory per-process store by default; multi-replica deployments need shared storage.
  • Sanitizes generated operation-key literals, uses a fixed CLI generation failure message, and suppresses smoke-test exception details that may include inherited environment values.
  • Uses a versioned crash-recovery journal, durable file and directory flushes, lock identity checks, compare-and-swap preconditions and one transaction for multi-capability installs.
  • Retries transient lock identity changes when one writer releases and another acquires the project lock; independent 8/32 process writer tests cover the handoff.
  • Measures 100 / 1,000 / 10,000 file mutations against v3.0.0 and verifies 8 / 32 concurrent writer processes. The measured durability latency cost is documented in docs/benchmarks/transactions.md.
  • Registers the explicit v2.0.0-to-v3.0.0 template upgrade, preserves unrelated TypeScript edits through AST-based integration, tracks shared-file migration bases and reports exact read-only plan diffs.
  • Orders migration chains by declared dependencies and validates manifest/state version preconditions and postconditions; synthetic multi-edge chain ordering and mismatched state versions are covered by tests.
  • Records the measured v2 upgrade-plan latency and memory comparison at 100 / 1,000 / 10,000 managed files in docs/benchmarks/upgrades.md.
  • Assembles capability Compose fragments into a validated file consumed by launchstack dev, and resolves package and lockfile writes together before committing the transaction.
  • Generates a BullMQ worker and cron scheduler with health-checked Redis startup and graceful process shutdown; documents OAuth, storage, observability, WebSocket, email and webhook helpers as helper-only.
  • Prevents removal of capabilities still required by another installed capability and removes generated worker/scheduler scripts safely.
  • Records 1k/10k-node and up to 100k-edge dependency planning, Redis readiness/shutdown and ten BullMQ roundtrips in docs/benchmarks/capabilities.md.
  • Gives development and preview projects unique Compose namespaces and dynamically allocated loopback ports; health checks wait for the API, worker and scheduler readiness endpoints.
  • Runs generated development migrations only on loopback databases, adds explicit local reset and seed safeguards, and emits structured service status.
  • Includes an optional generic local HTTP mock for development adapters, with an explicit note that it does not reproduce provider behavior.
  • Tracks child process groups through unexpected parent exit, cleans only the owned Compose project on failure or signals, and keeps database volumes during ordinary development shutdown.
  • Supports concurrent preview stages with collision-resistant resource identities, serialized port assignment, merged state updates and temporary BuildKit CA secrets when the host Node runtime supplies a certificate path.
  • Allocates Redis capability ports per environment and includes capability services throughout preview stage creation, inspection and teardown.
  • Verified two concurrent generated projects and two concurrent Docker preview stages from the packed candidate. Actual startup measurements and the comparison limits are in docs/benchmarks/orchestration.md.
  • Verified that occupied API and Redis defaults reassign safely and that the queue worker completes a real job through the dynamically configured Redis port.
  • Makes generated resource updates atomic with the owner predicate at the database mutation. Read/update/delete continue to return non-disclosing not-found responses for another owner. Lists use a bounded indexed keyset and return items, hasNext and nextCursor; tied timestamps and deletion between pages are covered against PostgreSQL.
  • Validates resource names, Prisma fields and generated route-prefix collisions before applying writes.
  • Generates SDKs from bounded OpenAPI 3.0/3.1 documents with local references, nullable and composed schemas, enums, parameter groups and response variants. All three targets are compiled and exercised with a fixture request server.
  • Scopes generated React query keys by canonical API base URL, operation method/path and caller-provided cache identity.
  • Observed database query counts and limits are recorded in docs/benchmarks/generators.md.
  • Keeps deterministic service ordering with heap-based scheduling at O((V+E) log V), and resolves extension dependency graphs in O(V+E) using an explicit stack that retains actionable cycle paths.
  • Hashes managed files in fixed 64 KiB chunks, records the file-byte cost and drift-report sorting in the README, and reuses one operation list while rendering OpenAPI client sections.
  • Adds structural tests for 10,000 service vertices, a 12,000-node extension chain, 24 MiB file hashing and descriptor cleanup. The complexity benchmark records graph/hash comparisons, process resource measurements and a V8 CPU profile in docs/benchmarks/complexity.md.

Release qualification

  • Adds the full release qualification harness and measured 250,000-file drift, graph, mutation, recovery, upgrade, packed CLI and generated API/PostgreSQL workloads. See docs/benchmarks/qualification.md and the raw JSON for methodology and results collected on the qualification host.
  • Matched CLI runs on v3.0.0 commit f76996cc0c3d125abcb1e6f998d2cc037c02b140 and the v3.0.4 candidate show higher startup and generation times in this sample. The candidate template contains 111 files versus 71 in v3.0.0.
  • Adds the v3.0.4 engineering summary and compatibility policy in docs/release/V3.0.4_RELEASE_SUMMARY.md and docs/COMPATIBILITY.md.
  • Adds Prettier, SBOM, Windows portability and CodeQL checks.
  • Fixes generated Compose and Render project-name placeholders and uses a Compose reset override to remove the development PostgreSQL host port from production. The local generated production image now passes its container health check and PostgreSQL readiness request.
  • The merged release passed local release:check on Node 24.22.3 and 26.13.1, and the production Docker image passed health/readiness checks. GitHub CI, Windows portability, TypeScript analysis and CodeQL passed. See LaunchStack CLI v3.0.4.

Verification

  • Post-merge main release checks passed on Node 24.22.3/PostgreSQL 16 and Node 26.13.1/PostgreSQL 17: 42 root test files / 179 tests and 9 generated-project test files / 28 tests on each runtime. The 1,290-case security corpus passed with observed peak RSS of 91.4 MiB and 96.0 MiB respectively.

  • Root release:check passed on Node 24.22.3 and 26.13.1; generated API integration checks passed on PostgreSQL 16 and 17 respectively.

  • After orchestration work, full release:check passed on both runtimes with 38 root test files / 137 tests and 8 generated API test files / 26 tests; both production dependency audits reported zero vulnerabilities.

  • Production dependency audits reported zero vulnerabilities for both the CLI and generated API.

  • The generated production Docker image passed its healthcheck and /health request.

  • Final GitHub CI and CodeQL pass on merged main. The v3.0.0-to-candidate CLI comparison is recorded in docs/benchmarks/runtime.md; warm startup timings were mixed.

  • At 100k and 250k managed files, the candidate upgrade dri...

Read more

LaunchStack CLI v3.0.0

Choose a tag to compare

@github-actions github-actions released this 14 Sep 20:26
f76996c

LaunchStack CLI v3.0.0

Release date: 2026-09-14

LaunchStack v3 turns the CLI from a one-time backend scaffolder into a project lifecycle platform while keeping user business logic outside LaunchStack ownership.

Highlights

Declarative project lifecycle

Fresh projects include launchstack.json plus .launchstack/state.json. plan, apply, reconcile, diff, upgrade --plan and doctor --fix operate from the same state model. Managed files carry hashes, so LaunchStack reports local drift instead of silently replacing changed code.

Composable capabilities and plugins

launchstack add installs first-party Redis, queues, OAuth, storage, observability, WebSockets, email, cron and webhook capability slices. Dependencies resolve topologically with cycle/conflict checks and idempotent re-application. Third-party plugins use schema-validated declarative manifests; path traversal and managed-file ownership conflicts are rejected, and executable hooks are never silently run.

Local orchestration, SDKs and generators

launchstack dev derives infrastructure/process ordering from installed capabilities. launchstack client generate creates deterministic typed clients from OpenAPI with injected auth and typed errors. launchstack generate module/resource preserves the generated layered architecture; CRUD data access is owner-scoped by default to avoid object-ID-only authorization patterns.

Production audit and preview stages

launchstack audit provides stable security/readiness rules with severity thresholds and reasoned suppressions. Preview/stage commands ship with a complete Docker Compose lifecycle adapter, source-commit/state tracking, deterministic isolated resource IDs and explicit production acknowledgement before destructive teardown.

Concurrency and efficiency

  • Concurrent mutating LaunchStack commands are serialized by a per-project exclusive lock.
  • Mutations are staged and journaled before commit and support stale/interrupted recovery.
  • Capability dependency planning is O(V+E).
  • Managed drift and reconciliation are O(M) in LaunchStack-owned entries plus file bytes read.
  • OpenAPI generation traverses paths/schema nodes once and uses deterministic collision suffixes.
  • Existing generated API database-enforced refresh-token and registration race tests remain in the release gate.

Issues addressed

This release implements the v3 roadmap tracked in #19 through #27: composable capabilities, project drift/upgrades, local orchestration, typed API clients, production audit, resource/module generation, preview/stage lifecycle, plugin recipes, and the declarative project manifest/reconciliation engine.

Upgrade

Existing v2 projects should review the plan first:

launchstack upgrade --plan
launchstack upgrade
launchstack doctor --fix

Ambiguous user edits are reported as conflicts and must be resolved explicitly.

Verification

The release is only considered complete after the exact PR head and merged main SHA pass npm run release:check, followed by a successful provenance-enabled npm publish and GitHub Release creation.

LaunchStack CLI v2.1.0

Choose a tag to compare

@github-actions github-actions released this 14 Sep 19:58
447567d

LaunchStack CLI v2.1.0

Release date: 2026-09-14

v2.1.0 is a hardening release focused on making the package users install match the security guarantees in source, strengthening generated authentication under concurrency, and turning the release pipeline into an artifact-level quality gate.

Highlights

The published artifact is now authoritative

LaunchStack verifies the result of npm pack from a clean install. The release gate checks that the installed client refuses unsafe HTTP origins, embedded URL credentials, and redirects that could forward API credentials. It also verifies that launchstack --version matches the package version and fails when committed dist/ output is stale relative to source.

Safer local secret handling

launchstack secrets add no longer accepts the secret value as a positional argument. Values are entered through hidden interactive input or --stdin, written atomically, stored with restrictive permissions where supported, and excluded from generated Git/Docker contexts.

Database-enforced refresh-token rotation

Generated APIs consume refresh tokens conditionally inside a Prisma transaction and create the successor token in that same transaction. A database-backed concurrency test proves that two simultaneous refreshes using one parent token produce exactly one successful rotation.

Generated API security baseline

Generated APIs now include auth-route rate limiting, bounded auth inputs, explicit production CORS rules, startup JWT duration validation, duplicate-email race handling, and a patched Swagger UI/static dependency line.

Honest deployment state

launchstack deploy builds and verifies deployment artifacts but records them as prepared until a remote provider adapter confirms deployment success. Prepared artifacts are not presented as successful rollback targets.

Hardened generation and Docker output

Project generation is staged transactionally before the destination is replaced. Template substitution is single-pass and avoids decoding binary/static assets as text. launchstack docker init and generated API projects now share a canonical Docker renderer with lockfile-driven installs, multi-stage builds, production-only runtime dependencies, secret-safe build contexts, and a non-root runtime user.

Reproducible, verified releases

The repository now uses lockfile-first CI, intentional semver ranges, Node.js 20-compatible runtime dependencies, linting, TypeScript typechecking, deterministic build-artifact checks, packed-artifact smoke tests, generated-project smoke tests, PostgreSQL-backed concurrency checks, and runtime vulnerability audits.

When a new version reaches main, the publish workflow reruns the full release gate, verifies the versioned release notes, creates the matching v<version> tag at the exact merged commit, publishes to npm with provenance using the LAUNCHSTACK_NPM_TOKEN repository secret, and creates the GitHub Release titled LaunchStack CLI v<version> from this file.

GitHub issues addressed

This release implements the correctness/security/performance hardening backlog tracked in issues #2 through #18, including credential-forwarding release integrity, secret storage, refresh-token concurrency, vulnerable generated dependencies, auth hardening, CORS, duplicate registration races, CI/release gating, deployment semantics, supply-chain reproducibility, JWT configuration validation, CLI version drift, transactional generation, template performance, Git subprocess reduction, Docker hardening, and provider consistency.

Breaking/behavior changes

  • launchstack secrets add API_KEY value is replaced by launchstack secrets add API_KEY (hidden prompt) or launchstack secrets add API_KEY --stdin.
  • launchstack deploy no longer records a local build as a successful remote deployment; it records prepared until remote confirmation exists.
  • Production generated APIs require explicit CORS origins by default.

Release verification

The release candidate must pass:

npm ci
npm run release:check

The merged main commit is verified again before tag creation or npm publishing. No release is considered complete until the exact merged commit has a green release gate and the npm/GitHub release workflow succeeds.

LaunchStack CLI v2.0.2

Choose a tag to compare

@wbizmo wbizmo released this 11 Jul 01:05

LaunchStack CLI v2.0.2

This release focuses on documentation polish and release consistency.

Highlights

  • Updated project version to v2.0.2 across the repository
  • Improved README with clearer installation, Quick Start and command documentation
  • Updated CHANGELOG
  • Improved package metadata consistency
  • Updated template metadata
  • Documentation refinements throughout the project

Quality

  • All project quality gates passed
  • Generated project validation passed
  • Release audit passed
  • Production runtime validation passed

Breaking Changes

None.

Upgrade

npm install -g launchstack-cli@2.0.2

Thank you to everyone who has supported LaunchStack CLI and provided feedback.

LaunchStack CLI v2.0.1

Choose a tag to compare

@wbizmo wbizmo released this 11 Jul 01:02

LaunchStack CLI v2.0.1

Documentation and release polish update following the v2.0.0 launch.

Improvements

  • Completely redesigned README
  • Improved installation guide
  • Improved Quick Start guide
  • Improved command documentation
  • Better project overview
  • Added generated project quality commands
  • Added production workflow documentation
  • Improved developer documentation
  • Better GitHub presentation
  • Better npm package presentation

Compatibility

This release contains no runtime or API changes.

Projects generated with LaunchStack CLI remain fully compatible with v2.0.0.

Upgrade

Install the latest version:

npm install -g launchstack-cli@2.0.1

Thank you to everyone who has tried LaunchStack CLI and provided feedback after the v2 release.

LaunchStack CLI v2.0.0

Choose a tag to compare

@wbizmo wbizmo released this 11 Jul 00:53

LaunchStack CLI v2.0.0

LaunchStack CLI v2 expands LaunchStack from a deployment workflow utility into a production-ready backend API scaffolding and developer workflow CLI.

Highlights

  • New launchstack create <project-name> command
  • Fastify and TypeScript API starter
  • Prisma ORM and PostgreSQL integration
  • JWT access and refresh-token authentication
  • Secure refresh-token rotation and revocation
  • Password hashing with bcrypt
  • Zod request and response validation
  • Swagger/OpenAPI documentation at /docs
  • Layered controllers, services, repositories, and DTOs
  • Structured application errors and response envelopes
  • Health, database health, and readiness endpoints
  • Docker and Docker Compose support
  • GitHub Actions CI and Docker workflows
  • Render, Railway, and Fly.io deployment presets
  • New launchstack doctor project health command
  • Generated architecture, deployment, README, and changelog documentation

Existing functionality retained

  • Project configuration initialization
  • Configuration validation
  • Environment switching
  • Provider management
  • Deployment workflow execution
  • Deployment history
  • Rollback target lookup
  • Local secrets management
  • Docker scaffolding
  • GitHub Actions generation

Generated project workflow

  1. Run launchstack create my-api
  2. Run cd my-api
  3. Run npm install
  4. Run npm run db:up
  5. Run npm run prisma:migrate -- --name init
  6. Run npm run dev

Swagger UI is available at http://localhost:3000/docs.

Quality verification

The release candidate passed:

  • LaunchStack unit and template tests
  • TypeScript build
  • npm package inspection
  • Installation from the packed npm tarball
  • Fresh project generation
  • Generated-project type checking
  • Generated-project tests
  • Generated-project production build
  • Docker image validation
  • PostgreSQL runtime validation
  • Registration and login flow
  • Protected profile access
  • Refresh-token rotation
  • Revoked-token rejection
  • Documentation and package-content audits

Installation

After npm publication, install with:

npm install -g launchstack-cli@2.0.0

Requirements

  • Node.js 20 or newer
  • PostgreSQL or Docker for database-backed development

See the updated README and generated documentation for setup, architecture, and deployment guidance.

LaunchStack CLI v1.0.0 — Initial Production Release

Choose a tag to compare

@wbizmo wbizmo released this 18 Jun 00:52

LaunchStack CLI v1.0.0

Initial production release of LaunchStack CLI, a TypeScript-based command-line tool for deployment automation, project configuration management, environment control, deployment tracking, and developer workflow tooling.

Features

  • Project initialization and configuration management
  • Configuration validation
  • Environment switching
  • Deployment provider management
  • Deployment workflow execution
  • Deployment history tracking
  • Rollback target lookup
  • Local secrets management
  • Git metadata tracking
  • Docker scaffolding generation
  • GitHub Actions workflow generation

Commands

  • launchstack init
  • launchstack status
  • launchstack validate
  • launchstack env
  • launchstack provider
  • launchstack deploy
  • launchstack history
  • launchstack rollback
  • launchstack secrets
  • launchstack docker init
  • launchstack github init

Technical Highlights

  • TypeScript
  • Node.js
  • Commander
  • Zod
  • Docker
  • GitHub Actions
  • Git integration
  • Local-first configuration architecture
  • Deployment history and rollback tracking

Project Goals

LaunchStack CLI was built to demonstrate practical developer tooling and DevOps-oriented workflow automation through a lightweight but production-ready command-line application. The project focuses on configuration management, deployment workflows, infrastructure scaffolding, and operational tooling commonly found in modern software delivery environments.

Author

Williams Ashibuogwu (wbizmo)

GitHub:
https://github.com/wbizmo