Don't deploy NPM modules when the release fails
What does this MR do?
Fixes an issue with the pipeline configuration that allowed the deploy-npm
job to run even though the previous release
job had failed. This can cause accidental overwriting of the deployed NPM module.
This fixes an issue introduced by !75 (merged) and was brought to our attention by @codejedi365. Thanks!
Availability and Testing
This has been tested on a personal fork of the schema project.
-
Review and add/update tests for this feature/bug
Edited by Cameron Swords