Skip to content

feat: fork release workflow — build tarball on tag, install from URL#9

Merged
thompsonson merged 1 commit into
mainfrom
feat/fork-release-workflow
Apr 29, 2026
Merged

feat: fork release workflow — build tarball on tag, install from URL#9
thompsonson merged 1 commit into
mainfrom
feat/fork-release-workflow

Conversation

@thompsonson
Copy link
Copy Markdown
Owner

Summary

  • New workflow .github/workflows/fork-release.yml triggers on v*-thompsonson.* tags
  • CI runs npm ci && npm run build && npm pack, renames to codeburn.tgz, attaches to GitHub release
  • chezmoi installs via npm install -g <release-tarball-url> — no build at install time

Why

npm install -g <github-url> fights with npm's --force flag and devDependency install ordering. Installing from a pre-built tarball bypasses all of that — npm just downloads, extracts, and links the binary.

Closes #7. Supersedes #8.

On push of v*-thompsonson.* tags, CI builds and attaches codeburn.tgz
to a GitHub release. Chezmoi installs from the tarball URL — no build
step at install time, bypasses npm GitHub install issues entirely.

Restores prepare to npm run build for local dev convenience.
@thompsonson thompsonson merged commit fe03a26 into main Apr 29, 2026
3 checks passed
@thompsonson thompsonson deleted the feat/fork-release-workflow branch April 29, 2026 10:34
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.

fix: npm install -g from GitHub fails when devDependencies missing at prepare time

1 participant