Skip to content

add support for publishing alpha branches to npm#86

Merged
nikrom17 merged 3 commits intomainfrom
feature/alpha-branch-support
Jan 6, 2026
Merged

add support for publishing alpha branches to npm#86
nikrom17 merged 3 commits intomainfrom
feature/alpha-branch-support

Conversation

@nikrom17
Copy link
Member

@nikrom17 nikrom17 commented Jan 6, 2026

Summary

Adds support for publishing alpha releases from non-main branches while keeping regular production releases on the main branch.

Changes

npm Scripts

  • Added prebuild:release script to deduplicate build logic
  • Added prerelease:alpha and postrelease:alpha lifecycle scripts for alpha releases
  • Modified release:alpha to use standard-version --prerelease alpha

GitHub Actions Workflow

  • Updated .github/workflows/publish.yml to detect current branch
  • Main branch: publishes regular releases with latest tag
  • Non-main branches: publishes alpha releases with alpha tag

How It Works

Regular Release (main branch):

# Trigger workflow from main branch
# Result: 5.8.0 → 5.9.0 (npm tag: latest)

Alpha Release (feature/dev branches):
# Trigger workflow from any other branch
# Result: 5.8.0 → 5.9.0-alpha.0 (npm tag: alpha)

Users can install alpha versions with:
npm install @krakenjs/beaver-logger@alpha

Benefits

- Safe testing of releases from feature branches
- Alpha releases don't affect production latest tag
- Single workflow handles both release types
- Automatic branch detection - no manual configuration needed

@nikrom17 nikrom17 changed the title Feature/alpha branch support add support for publishing alpha branches to npm Jan 6, 2026
@nikrom17 nikrom17 merged commit 41ef3d7 into main Jan 6, 2026
1 check passed
@nikrom17 nikrom17 deleted the feature/alpha-branch-support branch January 6, 2026 19:32
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.

3 participants