Skip to content

ci: release from the branch name, deploy docs only after npm publish - #59

Merged
samiodeh1337 merged 1 commit into
mainfrom
chore/release-pipeline
Oct 2, 2026
Merged

samiodeh1337 merged 1 commit into
mainfrom
chore/release-pipeline

Conversation

@samiodeh1337

@samiodeh1337 samiodeh1337 commented Oct 2, 2026 •

Copy link
Copy Markdown
Owner

Type

  • 🚀 Feature
  • 🐛 Bug Fix
  • ♻️ Refactor
  • 📝 Documentation
  • 🧹 Chore (dependencies, CI, tooling)

Description

  • release-branch.yml (new): creating release/X.Y.Z sets package.json, dates CHANGELOG.md, commits to the branch and opens
    the PR. Rejects bad names and already-released versi
  • release.yml: merging that PR checks package.json on main equals the branch version, then tags vX.Y.Z. Also runnable from
    the Actions tab.
  • publish.yml: on the tag, three jobs in order: the gate (plus tag = package.json), npm publish --provenance + GitHub
    Release, then the docs deploy. A failed publish stop
  • deploy-docs.yml: manual only, for docs-only redeploys.
  • ci.yml: also runs on pushes to release/**.

Checklist

  • I have read the Contributing Guide
  • My code follows the project's code style (ran npm run format)
  • I have run npm run lint with no errors
  • I have tested my changes locally
  • I have updated the documentation if needed
  • I have updated the CHANGELOG.md if applicable
  • My changes do not introduce any new warnings

@samiodeh1337
samiodeh1337 merged commit 670e2f0 into main Oct 2, 2026
1 check 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.

1 participant