When making a private extension release, we manually add a version suffix to the package so that it can be distinguished from an official release.
This PR automates that process in 2 ways:
(1) the CI automatically adds a version suffix when the standard/manual release pipeline is triggered in a feature branch. The version suffix will be -pr.<yyyymmdd.<buildRev>> where <buildRev> is an integer that increases every time the pipeline is triggered on a given day.
(2) the CI automatically adds a version suffix when the nightly release pipeline is triggered. The version suffix will be -ci.<yyyymmdd.<buildRev>> where <buildRev> is an integer that increases every time the pipeline is triggered on a given day.
Thanks @jviau - I agree it would be good to consolidate (and I agree it would be a good idea), but +1 to doing it later so we can benefit from the automation now. Thanks!
Replaces: https://github.com/Azure/azure-functions-durable-extension/pull/2707
When making a private extension release, we manually add a version suffix to the package so that it can be distinguished from an official release.
This PR automates that process in 2 ways:
(1) the CI automatically adds a version suffix when the standard/manual release pipeline is triggered in a feature branch. The version suffix will be
-pr.<yyyymmdd.<buildRev>>
where<buildRev>
is an integer that increases every time the pipeline is triggered on a given day. (2) the CI automatically adds a version suffix when the nightly release pipeline is triggered. The version suffix will be-ci.<yyyymmdd.<buildRev>>
where<buildRev>
is an integer that increases every time the pipeline is triggered on a given day.