Skip to content
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
merged 3 commits into from
Sep 1, 2020
Merged

Conversation

apetro
Copy link
Contributor

@apetro apetro commented Aug 21, 2020

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

  • The change has been examined for security impact.

PR considerations checklist:

  • N/A Updates CHANGELOG.md to reflect this PR's change.
  • This Contribution is under the terms of Individual Contributor License Agreements (and also Corporate Contributor License Agreements to the extent applicable) appearing in the Apereo CLA roster.

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.
@apetro apetro merged commit 8117cc0 into master Sep 1, 2020
@apetro apetro deleted the no-node-release branch September 1, 2020 15:45
@apetro apetro added this to the 17.0.1 milestone Sep 1, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants