-
Notifications
You must be signed in to change notification settings - Fork 0
feat(workflows): add release.yml reusable workflow for Node.js package releases #369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
neilime
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot handle feedbacks
neilime
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot handle feedbacks
neilime
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@copilot here are the existing workflows that should be replaced by the ".github/workflows/release.md" we are creating. Ensure that we will support all the scope and behavior:
- https://github.com/reactionable/reactionable/blob/main/.github/workflows/release.yml
- https://github.com/reactionable/reactionable-cli/blob/main/.github/workflows/release.yml
- https://github.com/escemi-tech/ts-dev-tools/blob/main/.github/workflows/release.yml
- https://github.com/hoverkraft-tech/ci-dokumentor/blob/main/.github/workflows/main-ci.yml#L46
- https://github.com/hoverkraft-tech/docusaurus-theme/blob/main/.github/workflows/main-ci.yml#L27
Analyzed all referenced workflows and added support for their use cases: Added features:
Supported workflows:
The workflow now supports publishing from source, build artifacts, or pre-built tarballs. Commit 56b60f9. |
Co-authored-by: neilime <314088+neilime@users.noreply.github.com>
…flow Co-authored-by: neilime <314088+neilime@users.noreply.github.com>
…rkflow Co-authored-by: neilime <314088+neilime@users.noreply.github.com>
…control Co-authored-by: neilime <314088+neilime@users.noreply.github.com>
…ct download path Co-authored-by: neilime <314088+neilime@users.noreply.github.com>
1bba531 to
0b53353
Compare
|
Code Coverage Report Coverage ResultsCoverage
Overall: 100.00% 🟢 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #369 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 1 1
Lines 3 3
=========================================
Hits 3 3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Adds a reusable workflow for releasing Node.js packages with support for multiple registries, optional documentation generation, and integration with CI build artifacts.
Features
publicorrestricted)latest,next,canary, etc.Usage
Basic Release from Source
Release with Build Artifacts from CI
Release Pre-built Tarball
Workflow Compatibility
This workflow replaces and consolidates release functionality from existing workflows:
Changes
.github/workflows/release.yml— reusable workflow.github/workflows/release.md— comprehensive documentationREADME.md— reference to new workflowOriginal prompt
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.