This repository has been archived by the owner on May 4, 2022. It is now read-only.
drop npm release steps from releasing docs #985
Merged
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.
The npm release is a distraction. The way the uportal-app-framework is in practice adopted by downstream applications is via overlay on its Maven artifacts. So keep the Maven release steps, drop the npm step, one less thing to do when releasing.
Review for security considerations
PR considerations checklist:
CHANGELOG.md
to reflect this PR's change.