-
Notifications
You must be signed in to change notification settings - Fork 25
Open
Description
Enter your suggestions in details:
Goal: Publish the doc-kit package on npm as @node-core/doc-kit.
Automation: Use a similar workflow for automatically publishing the package on a new version bump as implemented for @node-core/ui-components in the @nodejs/nodejs.org repository.
Details:
- Automate the npm publish process so that every time a new version of
@node-core/doc-kitis released, it is automatically published to npm. - Use GitHub Actions to implement this automation, leveraging the workflow already established for
@node-core/ui-componentsin@nodejs/nodejs.orgas a reference. - The
publish.mjsscript in ui-components generates a cleanedpackage.jsonindist/, copies documentation, and runspnpm publish --no-git-checksin thedistdirectory. - The workflow is set up so publishing is triggered on merges to
main(after CI success) or viaworkflow_dispatch. More info and diagrams: docs/package-publishing.md. - The monorepo structure supports independent package publishing managed by GitHub Actions.
- Document any secrets (npm tokens), configuration steps, or permission requirements for publishing—including any changes needed for branch protection, secrets, or CI.
Plan:
- Review
ui-componentspublish script and docs. - Adapt a similar workflow and script for use in
doc-kit(ensure it strips devDependencies, formats paths, and publishes fromdist/). - Create a GitHub Action to trigger the publish job after a version bump, following merge to main or manual trigger—ensure it depends on the successful completion of tests.
- Test by bumping
@node-core/doc-kitversion and verifying an automated npm publish. - Document the setup and maintenance steps in the repository README.
References:
ljharb and araujoguiavivkeller
Metadata
Metadata
Assignees
Labels
No labels