Automatically generate version suffixes for private releases of DTFx.AS and DTFx.Core #918
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.
When making a private extension release, we usually add a version suffix to the package so that it can be distinguished from an official release.
This PR automates that process so that the CI automatically adds a version suffix when the release pipeline is triggered in a feature branch. The version suffix will be
-preview.<buildVersion>
where<buildVersion>
is automatically generated by the CI.Since multiple groups work in this repo, I've only made this change for DTFx.AS and DTFx.Core. In order to achieve that, I created a copy of the release pipeline yaml and filtered it to only apply to those two packages.