chore: add github workflow for npm publish #1073
Merged
Conversation
This file contains 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
mrnaveira
changed the title
Test Results (CI)540 tests 540 ✅ 1h 47m 4s ⏱️ Results for commit 6ddc4ce. |
sdbondi
approved these changes
Jul 10, 2024
3 tasks
sdbondi
added a commit
that referenced
this pull request
Jul 10, 2024
Description --- Fixes the package location problems of #1073 Motivation and Context --- Does not apply How Has This Been Tested? --- Does not apply What process can a PR reviewer use to test or verify this change? --- Does not apply Breaking Changes --- - [x] None - [ ] Requires data directory to be deleted - [ ] Other - Please specify --------- Co-authored-by: Stan Bondi <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
Added a new github CI action to automatically publish to npm registry on every version change::
Motivation and Context
The
typescript-bindingsand thewallet-daemon-clientnpm packages are used by multiple projects. We want to automatically publish their latest versions to the NPM registry when the package versions increases. This way dependent projects can directly include the npm dependency for them.How Has This Been Tested?
In progress
What process can a PR reviewer use to test or verify this change?
Testing in progress
Breaking Changes