yashdev9274 / yashdev9274/supercli
Automated npm publishing — CI workflow on tag push
Open
Nobody has claimed this yet.
CI/CD
repo core
supercode-cli
- Dominant language
- TypeScript
- Stars
- 214
- Forks
- 41
- Avg merge
- 2h 26m
- Merged PRs (30d)
- 34
Description
Description
Set up a GitHub Actions workflow that automatically publishes supercode-cli to npm when a new version tag is pushed.
Expected Deliverables
.github/workflows/publish.ymltriggered onv*.*.*tags- Steps: checkout → setup Bun → install → build → test → publish
- Uses
NPM_TOKENsecret - Pre-publish validation (version matches tag, dry-run)
- Document release workflow in CONTRIBUTING.md
Why
Currently publishing is manual. Automation removes human error and ensures every tag results in a published package.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the expected workflow at .github/workflows/publish.yml and the release guidance in CONTRIBUTING.md. Implement the tag-triggered sequence of checkout, Bun setup, install, build, test, validation, dry-run, and publish using NPM_TOKEN. Done means matching v*.. tags publish successfully and the documented release workflow explains the version and pre-publish checks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bun, github-actions, typescript
- Domain
- ci-cd, documentation, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 68/100