You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: Add new release pipeline with production template (#1262)
#### Details
Added new yml file for production release using production template and
EnableSemanticRelease variable. Also moved the common code between CI
and release pipeline to common template.
The new release pipeline will be added mseng ADO as it requires access
to key vault for getting github and npm publish tokens.
To create pipeline in mseng ADO, yaml file should be available in main
branch so I will create and test the new release pipeline after merging
this PR.
##### Motivation
<!-- This can be as simple as "addresses issue #123" -->
##### Context
<!-- Are there any parts that you've intentionally left out-of-scope for
a later PR to handle? -->
<!-- Were there any alternative approaches you considered? What
tradeoffs did you consider? -->
#### Pull request checklist
<!-- If a checklist item is not applicable to this change, write "n/a"
in the checkbox -->
- [x] PR title respects [Conventional
Commits](https://www.conventionalcommits.org) (starts with `fix:`,
`feat:`, etc, and is suitable for user-facing release notes)
- [x] PR contains no breaking changes, **OR** description of both PR
**and final merge commit** starts with `BREAKING CHANGE:`
- [n/a] (if applicable) Addresses issue: #0000
- [n/a] Added relevant unit tests for your changes
- [x] Ran `yarn precheckin`
- [n/a] Verified code coverage for the changes made
0 commit comments