GitHub package registry deployment action #61
Closed
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
|
Closing PR, since the changes are moved to #60, to start using the action in that PR |
|
Right. I noticed the npm stuff over there. I'll take this PR off the board. |
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.
What this PR does / why we need it:
Introduces an automated GitHub action to be executed on PR commits.
The action builds and deploys the package to a new GitHub npm registry (https://github.com/IQSS/dataverse-client-javascript/pkgs/npm/dataverse-client-javascript), dedicated to development images from PRs only. This way the SPA can use these versions to test the changes developed in the package during the PRs.
Which issue(s) this PR closes:
Special notes for your reviewer:
Versioning format followed for the pushed packages:
<NEXT_RELEASE_VERSION>-pr<PR_NUMBER>.<SHORTENED_COMMIT_HASH>
Example:
2.0.0-pr61.8ac5f25
Suggestions on how to test this:
N/A
Is there a release notes update needed for this change?:
No
Additional documentation:
N/A