chore(release): v0.12.1

[jal-co]

What

Release v0.12.1 — a patch bump in package.json (and lockfile) to ship the merged CLI fixes to npm.

Why

#42 is on main but not yet published, so users still get the old behaviour (required prompts + the mkdir '/orc' crash). This bump lets a GitHub Release publish the fix.

Since the package is in initial development (0.y.z) and #42 is a bug fix, this is a PATCH bump per SemVer — 0.12.0 → 0.12.1.

Included since v0.12.0

• fix(cli): make project location + github repo optional, guard bad dirs (fix(cli): make project location + github repo optional, guard bad dirs #42)
  • Project location optional (falls back to ./<name>)
  • GitHub owner/repo optional (<owner>/<name> placeholder)
  • Refuse out-of-tree scaffold dirs instead of crashing with mkdir ENOENT

Note: #41 (website light mode) is www/-only and ships via Vercel — not part of the npm package.

How

npm version 0.12.1 --no-git-tag-version (the vX.Y.Z tag is created by the GitHub Release, which triggers publish.yml).

Type

• feat — New feature
• fix — Bug fix
• docs — Documentation
• refactor — Code restructuring
• perf — Performance improvement
• style — Formatting / code style
• chore — Maintenance / deps
• ci — CI/CD changes
• test — Tests

Checklist

• Branch follows conventional naming (release/)
• Commits follow Conventional Commits
• npm run lint passes
• npm test passes (103 tests)
• Tests added or updated (n/a — version bump only)
• Docs updated (n/a)

Release steps (after merge)

1. Merge this PR (release branches use a merge commit).
2. Create a GitHub Release tagged v0.12.1 targeting main → publish.yml lints, builds, tests, and runs npm publish --provenance.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
scn-stack	Ready	Preview, Comment	Jun 15, 2026 3:57am