@bensandee/tooling 0.13.0 → 0.14.1

package/CHANGELOG.md

@@ -0,0 +1,225 @@
+# @bensandee/tooling
+
+## 0.14.1
+
+### Patch Changes
+
+- caeebd8: Add d.ts declaration file output and types export conditions
+- caeebd8: Bump tsdown from 0.21.0 to 0.21.2
+- Updated dependencies [caeebd8]
+- Updated dependencies [caeebd8]
+  - @bensandee/common@0.1.2
+
+## 0.14.0
+
+### Minor Changes
+
+- e95d449: Add `--fail-fast` / `--no-fail-fast` flag to `checks:run` to control whether execution stops on the first failure. Defaults to fail-fast in dev and continue-on-error in CI.
+- 715a4ea: Add `@bensandee/tooling/docker-verify` subpath export: a TypeScript framework for Docker image verification with compose lifecycle management, HTTP health polling, container health monitoring, and signal-safe cleanup. Consumers import building blocks and compose them with custom validators instead of writing boilerplate.
+- 27c3480: Add `release:simple` command and rename CLI subcommands
+
+  **Breaking changes:**
+
+  - `release:create-forgejo-release` renamed to `forgejo:create-release`
+  - `release:merge` renamed to `changesets:merge`
+  - `releaseStrategy: "commit-and-tag-version"` renamed to `"simple"` in `.tooling.json` config
+  - Generated CI workflow for commit-and-tag-version now uses `pnpm exec tooling release:simple` instead of inline shell commands
+
+  **New feature:**
+
+  `release:simple` — a CLI command that handles the full release lifecycle for projects using commit-and-tag-version:
+
+  - Runs `commit-and-tag-version` to bump version, update CHANGELOG, and create a git tag
+  - Pushes to origin with `--follow-tags`
+  - Creates sliding version tags (vX, vX.Y) for flexible deployment pinning
+  - Creates Forgejo or GitHub releases automatically
+
+### Patch Changes
+
+- 715a4ea: Add README files to all published packages for npm registry documentation
+- 27c3480: Pre-populate `repo:init` prompts from saved `.tooling.json` config
+
+  When re-running `repo:init` on a project with an existing `.tooling.json`, each prompt now defaults to the previously saved choice instead of the detection-based default. Press Enter to keep existing settings or change only what you need.
+
+- d448ec6: Update node tsconfig base to use `nodenext` module resolution with `allowImportingTsExtensions`, enabling `.ts` extensions in imports for projects running TypeScript natively on Node 24+. Migrate all tooling-cli imports to use `.ts` extensions and switch `#src` subpath mapping to `#src/*.ts`. Use extensionless imports for library packages.
+- c49593f: Add `commit-and-tag-version` and `@changesets/cli` as optional dependencies
+
+  These tools are only needed when using their respective release strategies, so they're optional rather than required. Target projects already install them as devDependencies via the package-json generator.
+
+- Updated dependencies [715a4ea]
+- Updated dependencies [d448ec6]
+  - @bensandee/common@0.1.1
+
+## 0.13.0
+
+### Minor Changes
+
+- bbe3634: Add `checks:run` command (renamed from `repo:run-checks`). Add `ci:check`, `tooling:check`, and `tooling:update` as generated package.json scripts. CI workflows now run `pnpm ci:check`. Managed scripts are updated on `repo:update`/`repo:check` if they don't reference the expected command.
+
+### Patch Changes
+
+- f20b25d: `checks:run` now reads package.json to detect which scripts are defined. Undefined scripts show "(not defined)" instead of silently passing. Commands use `pnpm run` instead of `pnpm run --if-present`.
+
+## 0.12.0
+
+### Minor Changes
+
+- 5de6090: Add `repo:run-checks` command that runs all standard checks (build, typecheck, lint, test, format, knip, tooling:check, image:check) without short-circuiting, reporting a summary of failures at the end. Supports `--skip` to skip specific checks and `--add` to append custom checks. Generated CI workflows now use `pnpm check`, and the package.json generator produces `check` and `tooling:check` scripts pointing to this command. Managed scripts (`check`, `tooling:check`) are updated on `repo:update`/`repo:check` if they don't already reference the expected command.
+
+## 0.11.0
+
+### Minor Changes
+
+- 493ae65: Add `repo:run-checks` command that runs all standard checks (build, typecheck, lint, test, format, knip, repo:check) without short-circuiting, reporting a summary of failures at the end. Generated CI workflows and package.json `check` scripts now use this command. Skip `trigger-release` script for changesets release strategy.
+
+### Patch Changes
+
+- ae18571: Add .pnpm-store to gitignore file
+- 916c1ee: Ensure `yaml-language-server` schema comment is added to existing Forgejo workflow files during update/merge
+
+## 0.10.1
+
+### Patch Changes
+
+- f131a3d: Add `pnpm why` to the allowed Bash commands in generated Claude settings
+- 1cb2ce8: Add yaml-language-server schema comments to generated Forgejo workflow files and update schema glob to match both .yml and .yaml extensions
+
+## 0.10.0
+
+### Minor Changes
+
+- 34a0e1e: feat: merge missing config into existing lefthook and CI workflow files instead of skipping
+
+  Generators for `lefthook.yml`, CI check workflows, and release workflows now merge required
+  entries into existing files rather than silently skipping them. This means `repo:update` can
+  add new steps (e.g. a newly required CI check) to repos that were initialized before the step
+  existed.
+
+  Add `# @bensandee/tooling:ignore` in the first 10 lines of any YAML file to opt out of
+  automatic merging.
+
+### Patch Changes
+
+- 330cc2c: fix: use semantic JSON comparison in repo:check and repo:update to ignore formatting-only differences
+
+## 0.9.0
+
+### Minor Changes
+
+- 88f2a93: Require `.tooling.json` for `repo:update` and `repo:check` commands. Previously these commands would warn and continue with detected defaults when `.tooling.json` was missing, which could cause unexpected overwrites without proper archiving. Now they exit with an error directing the user to run `tooling repo:init` first.
+
+  Write Forgejo workflow schema mapping to `.code-workspace` file when present, falling back to `.vscode/settings.json`. The `yaml.schemas` setting in `.vscode/settings.json` doesn't apply in VS Code multi-root workspaces.
+
+  Improve post-init guidance: suggest a Claude Code prompt ("Execute the steps in .tooling-migrate.md") instead of "paste contents".
+
+## 0.8.1
+
+### Patch Changes
+
+- efcfdcc: Fix findOpenPr to filter PRs client-side by head.ref instead of relying on Forgejo's inconsistent head query parameter, which could match the wrong PR
+- 88aac23: Add forgejo workflow schema additions
+- e4c41d6: Fix wrong agent name in settings.json for claude
+- 43509b8: Pin @bensandee/\* package versions in generated package.json instead of using "latest". Versions are read from sibling package.json files at build time via tsdown's define feature, so they auto-update with each release.
+- 5e65e50: enhance ciWorkflow to support Forgejo email notifications
+- 60a5502: refactor generateClaudeSettings to handle monorepo structure and update tests for plugin integration
+
+## 0.8.0
+
+### Minor Changes
+
+- 375f7fd: Add claude skills to settings.json
+
+### Patch Changes
+
+- 375098b: Add more safety restrictions to settings.json
+- b330adf: Fix bad update to tsconfig when not needed
+
+## 0.7.3
+
+### Patch Changes
+
+- 3257e04: Fix no-unsafe-json-parse rule and fix new lint errors
+- ca61fa7: Don't overwrite existing oxfmt config
+- 1bdf858: More intelligent addition of src folder to tsconfig
+- 8de49b9: Add line about adding packages when necessary to resolve errors
+
+## 0.7.2
+
+### Patch Changes
+
+- e48bc27: Fix bug where tsconfigs in packages would be force-updated even if solutions-style
+
+## 0.7.1
+
+### Patch Changes
+
+- 6ef4ea9: Fix tsconfig build/update issues
+- 3608a1a: Run pnpm update after repo:update
+
+## 0.7.0
+
+### Minor Changes
+
+- 912013d: Add repo:check command
+- 2545262: Add common package + error subclasses
+
+### Patch Changes
+
+- Updated dependencies [2545262]
+  - @bensandee/common@0.1.0
+
+## 0.6.2
+
+### Patch Changes
+
+- caa1270: Fix hang migrating repo:init
+
+## 0.6.1
+
+### Patch Changes
+
+- 2182ab3: fix bug where renovate.json5 wasn't cleaned up to use our preset
+- d811a96: Lefthook doesn't need an install step in package.json prepare
+
+## 0.6.0
+
+### Minor Changes
+
+- 94cd161: Updated default oxlint config to include more default rules.
+
+## 0.5.1
+
+### Patch Changes
+
+- e0bc32e: Improve migration for tsconfig and husky/lint-staged
+- 02c1a1b: Include version when running tooling cli
+
+## 0.5.0
+
+### Minor Changes
+
+- 58fc8a3: Add lefthook support in place of husky, lint-staged
+
+## 0.4.0
+
+### Minor Changes
+
+- e02953a: Bug fixing, move renovate config to standard location
+- 451908d: Restructure package names and exports.
+
+## 0.3.0
+
+### Minor Changes
+
+- 5e9719f: Many bug fixes
+
+## 0.2.0
+
+### Minor Changes
+
+- c376981: Initial release
+
+### Patch Changes
+
+- 3fc9fe3: Support multiple release architectures (release-it, commit-and-tag-version and changsets)
+- 4004530: Add release-forgejo command to perform final steps of release creation in forgejo.

package/README.md

@@ -0,0 +1,121 @@
+# @bensandee/tooling
+
+CLI to bootstrap and maintain standardized TypeScript project tooling.
+
+## Installation
+
+```bash
+pnpm add -D @bensandee/tooling
+
+# Or run directly
+pnpm dlx @bensandee/tooling repo:init
+```
+
+## CLI commands
+
+### Project management
+
+| Command                     | Description                                                                                                             |
+| --------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| `tooling repo:init [dir]`   | Interactive setup wizard. Flags: `--yes` (accept defaults), `--no-ci`, `--no-prompt`. Saves choices to `.tooling.json`. |
+| `tooling repo:update [dir]` | Add missing config files (never overwrites existing files).                                                             |
+| `tooling repo:check [dir]`  | Dry-run drift detection. Exits 1 if files would change. CI-friendly.                                                    |
+| `tooling checks:run`        | Run project checks (build, typecheck, lint, knip, test). Flag: `--fail-fast`.                                           |
+
+### Release management
+
+| Command                          | Description                                                                                                                     |
+| -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
+| `tooling release:changesets`     | Changesets version/publish for Forgejo CI. Flag: `--dry-run`. Env: `FORGEJO_SERVER_URL`, `FORGEJO_REPOSITORY`, `FORGEJO_TOKEN`. |
+| `tooling release:simple`         | Streamlined release using commit-and-tag-version.                                                                               |
+| `tooling release:trigger`        | Trigger a release workflow.                                                                                                     |
+| `tooling forgejo:create-release` | Create a Forgejo release from a tag.                                                                                            |
+| `tooling changesets:merge`       | Merge a changesets version PR.                                                                                                  |
+
+## Config file
+
+`repo:init` persists choices to `.tooling.json` at the project root. `repo:check` and `repo:update` read this file to reproduce the same config without re-prompting.
+
+## Library API
+
+The `"."` export provides type-only exports for programmatic use:
+
+```ts
+import type {
+  ProjectConfig,
+  GeneratorResult,
+  GeneratorContext,
+  Generator,
+  DetectedProjectState,
+  LegacyConfig,
+} from "@bensandee/tooling";
+```
+
+| Type                   | Description                                                                                     |
+| ---------------------- | ----------------------------------------------------------------------------------------------- |
+| `ProjectConfig`        | User config shape (persisted in `.tooling.json`)                                                |
+| `GeneratorContext`     | Context passed to generator functions (`exists`, `read`, `write`, `remove`, `confirmOverwrite`) |
+| `GeneratorResult`      | Result from a generator (created/updated/skipped files)                                         |
+| `Generator`            | Generator function signature: `(ctx: GeneratorContext) => Promise<GeneratorResult>`             |
+| `DetectedProjectState` | Detected existing project state (package manager, CI, etc.)                                     |
+| `LegacyConfig`         | Legacy config detection for migration                                                           |
+
+## Docker verification
+
+The `@bensandee/tooling/docker-verify` export provides utilities for verifying Docker Compose stacks via health checks.
+
+### Quick start
+
+```ts
+import { createRealExecutor, runVerification } from "@bensandee/tooling/docker-verify";
+import type { VerifyConfig } from "@bensandee/tooling/docker-verify";
+
+const config: VerifyConfig = {
+  compose: {
+    cwd: "./deploy",
+    composeFiles: ["docker-compose.yaml"],
+    services: ["api", "db"],
+  },
+  buildCommand: "pnpm image:build",
+  healthChecks: [
+    {
+      name: "API",
+      url: "http://localhost:3000/health",
+      validate: async (res) => res.ok,
+    },
+  ],
+  timeoutMs: 120_000,
+  pollIntervalMs: 5_000,
+};
+
+const result = await runVerification(createRealExecutor(), config);
+if (!result.success) {
+  console.error(result.reason, result.message);
+}
+```
+
+### Exports
+
+| Export                                 | Description                                                       |
+| -------------------------------------- | ----------------------------------------------------------------- |
+| `runVerification(executor, config)`    | Full lifecycle: build, compose up, health check polling, teardown |
+| `createRealExecutor()`                 | Production executor (real shell, fetch, timers)                   |
+| `composeUp(executor, config)`          | Start compose services                                            |
+| `composeDown(executor, config)`        | Stop and remove compose services                                  |
+| `composeLogs(executor, config)`        | Stream compose logs                                               |
+| `composePs(executor, config)`          | List running containers                                           |
+| `checkHttpHealth(executor, check)`     | Run a single HTTP health check                                    |
+| `getContainerHealth(executor, config)` | Check container-level health status                               |
+
+### Types
+
+| Type                   | Description                                                                                |
+| ---------------------- | ------------------------------------------------------------------------------------------ |
+| `VerifyConfig`         | Full verification config (compose settings, build command, health checks, timeouts)        |
+| `ComposeConfig`        | Docker Compose settings (cwd, compose files, env file, services)                           |
+| `HttpHealthCheck`      | Health check definition (name, URL, validate function)                                     |
+| `VerifyResult`         | Result: `{ success: true, elapsedMs }` or `{ success: false, reason, message, elapsedMs }` |
+| `DockerVerifyExecutor` | Side-effect abstraction (exec, fetch, timers) for testability                              |
+| `ContainerInfo`        | Container status info from `composePs`                                                     |
+
+## [Changelog](./CHANGELOG.md)

package/dist/bin.d.mts

@@ -0,0 +1 @@
+export { };