fix(ci): preserve auth and build before npm publish#8
Merged
stevenobiajulu merged 1 commit intomainfrom Feb 25, 2026
Merged
Conversation
Release preflight now passes, but publish-suite failed with ENEEDAUTH because auth was explicitly unset right before npm publish.\n\nAlso, publish-suite runs in a fresh checkout, so dist artifacts were missing and tarballs would have been incomplete. Build the publishable packages in publish-suite and keep auth intact for trusted publishing. Add --provenance for signed provenance metadata.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary:\n- build publishable packages in release publish-suite\n- stop removing npm auth right before publish\n- add npm publish --provenance\n\nWhy:\nRelease preflight passes, but publish-suite failed with ENEEDAUTH because auth was unset in the publish step. Also, publish-suite starts from a fresh checkout, so dist artifacts were missing and tarballs would be incomplete without an in-job build.\n\nValidation:\n- npm run build -w @usejunior/docx-core\n- npm run build -w @usejunior/docx-mcp\n- npm run build -w @usejunior/safe-docx\n