[DYN-2316] implement GitHub actions to publish librarie js npm package for every release #213
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
|
Please also update the package name in package.json and package-lock.json, please use |
Enzo707
force-pushed
the
DYN-2316/add-github-actions-to-publish-librarieJS-npm-package-after-every-release
branch
from
62fb6d4 to
885f941
Compare
Done! |
QilongTang
reviewed
Mar 28, 2024
| @@ -1,5 +1,5 @@ | |||
| { | |||
| "name": "dynamo-hosted-contents", | |||
| "name": "@dynamods/librarieJS", | |||
There was a problem hiding this comment.
@Enzo707 Also it looks like there is no version info here so publish would not work correctly. You can use version 1.0.0
|
QilongTang
approved these changes
Mar 28, 2024
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.
This PR includes Github Actions build and npm-publish for package management uses and remove deployment step in pipeline to ditch Nuget package management.
Review:
@QilongTang