Skip to content

build: initialize LaunchKey workspace tooling#1

Merged
endalk200 merged 5 commits into
mainfrom
chore/commit-launchkey-workspace
Jun 4, 2026
Merged

build: initialize LaunchKey workspace tooling#1
endalk200 merged 5 commits into
mainfrom
chore/commit-launchkey-workspace

Conversation

@endalk200

Copy link
Copy Markdown
Owner

Adds the Bun workspace, Turborepo task graph, Biome formatting/linting configuration, shared TypeScript and Biome config packages, and repository ignore rules so package-level quality gates can run consistently.

endalk200 added 5 commits June 4, 2026 21:28
Adds the Bun workspace, Turborepo task graph, Biome formatting/linting configuration, shared TypeScript and Biome config packages, and repository ignore rules so package-level quality gates can run consistently.
Adds the shared configuration service for LaunchKey, including TOML file loading, environment override precedence, strict telemetry parsing, config file initialization, validation reports, and Effect layer integration.
Adds the public launchkey executable with Effect CLI wiring, version output, config path/init/validate commands, opt-in OTLP telemetry support, user-facing failure handling, and command/runtime tests.
Adds pinned GitHub Actions for CI, CodeQL, dependency audit, Changesets release PRs, and staged npm publishing. Includes release helper scripts for building the CLI, syncing version metadata, auditing dependencies, verifying package contents, and smoke-testing the packed executable.
Adds the initial project context, root README and license, architecture decisions for runtime, telemetry, configuration, CI/security gates, and npm release governance, plus operational notes for CI/CD and release handling.
@endalk200 endalk200 self-assigned this Jun 4, 2026
@github-advanced-security

Copy link
Copy Markdown

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

  • The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
  • Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
  • You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

@endalk200 endalk200 merged commit 9a70bb0 into main Jun 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants