Skip to content

fix(ci): publish to GitHub Packages with Node 24 + actions v6#3

Merged
yash-giantanalytics merged 2 commits intomainfrom
chore/ci-pr-only
Mar 28, 2026
Merged

fix(ci): publish to GitHub Packages with Node 24 + actions v6#3
yash-giantanalytics merged 2 commits intomainfrom
chore/ci-pr-only

Conversation

@yash-giantanalytics
Copy link
Copy Markdown

Summary

  • CI only runs on pull_request (not push to main — avoids redundant runs)
  • Release workflow publishes to GitHub Packages via changeset publish
  • Upgraded to Node.js 24 (current LTS) and actions/setup-node@v6
  • Removed redundant publish.yml (release.yml handles everything)
  • Added publishConfig.registry to react + collab package.json
  • Includes patch changeset to trigger new version (0.1.1) and publish

What happens after merge

  1. Release workflow runs on push to main
  2. Changesets detects the changeset file → opens Version PR (bumps to 0.1.1)
  3. Merge Version PR → changesets runs changeset publish
  4. setup-node with registry-url: npm.pkg.github.com + NODE_AUTH_TOKEN → publishes to GitHub Packages
  5. Frontend can then bun add @eigenpal/docx-js-editor@0.1.1

- release.yml: use actions/checkout@v6, actions/setup-node@v6,
  Node.js 24 (current LTS), registry-url for GitHub Packages,
  NODE_AUTH_TOKEN from GITHUB_TOKEN
- Remove publish.yml (redundant — release.yml handles publish)
- Add publishConfig.registry to react + collab package.json
  pointing to npm.pkg.github.com
- Add changeset for patch version bump to re-trigger publish
@yash-giantanalytics yash-giantanalytics merged commit 3f58005 into main Mar 28, 2026
2 checks passed
@yash-giantanalytics yash-giantanalytics deleted the chore/ci-pr-only branch March 28, 2026 01: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.

1 participant