Hey openap-validator folks! This PR should only make your lives easier. I'm not changing anything other than adding a release stage to our build yml. The reason I'm doing this is because we going after the long-tail of builds that cannot be converted to 1es-templates-compatible. The staging and prod releases to NPM for azure-openapi-validator need to be removed, but we also need to be certain you can still ship new versions of the package!
This PR will make it so that your prod and staging builds will also include approvable releases to npm.
In a nutshell, when you queue Staging or Production pipeline, you will immediately get an approvable release stage. Have to kick the pipeline manually to get the release stage.
Prod stage will be labeled release latest. These are also the tags that are set on the ERSP release.
Submitting this PR early to understand which CI will actually trigger.
Can one of the openapivalidator devs please confirm the two sets of artifacts on each linked release under the Test a release checkbox? Would I break anyone if I actually released a new version of the package?
Hey openap-validator folks! This PR should only make your lives easier. I'm not changing anything other than adding a release stage to our build yml. The reason I'm doing this is because we going after the long-tail of builds that cannot be converted to
1es-templates-compatible. The staging and prod releases to NPM for azure-openapi-validator need to be removed, but we also need to be certain you can still ship new versions of the package!This PR will make it so that your prod and staging builds will also include approvable releases to npm.
In a nutshell, when you queue
StagingorProductionpipeline, you will immediately get an approvable release stage. Have to kick the pipeline manually to get the release stage.Prod stage will be labeled
release latest. These are also the tags that are set on the ERSP release.todo:
Submitting this PR early to understand which CI will actually trigger.
Can one of the openapivalidator devs please confirm the two sets of artifacts on each linked release under the
Test a releasecheckbox? Would I break anyone if I actually released a new version of the package?