Why is this PR required? What issue does it fix?:
Earlier We were tagging release with semantic version 1.x.x, which is changed to v1.x.x. This PR fixes the tagging for downstream repo with new semver.
What this PR does?:
Earlier We were tagging release with semantic version 1.x.x, which is changed to v1.x.x. This PR fixes the tagging for downstream repo with new semver.
Does this PR require any upgrade changes?:
No
If the changes in this PR are manually verified, list down the scenarios covered::
NA
Any additional information for your reviewer? :
NA
Checklist:
[ ] Fixes # : NA
[ ] PR Title follows the convention of <type>(<scope>): <subject>: yes
Why is this PR required? What issue does it fix?: Earlier We were tagging release with semantic version 1.x.x, which is changed to v1.x.x. This PR fixes the tagging for downstream repo with new semver.
What this PR does?: Earlier We were tagging release with semantic version 1.x.x, which is changed to v1.x.x. This PR fixes the tagging for downstream repo with new semver.
Does this PR require any upgrade changes?: No
If the changes in this PR are manually verified, list down the scenarios covered:: NA
Any additional information for your reviewer? : NA
Checklist:
<type>(<scope>): <subject>
: yesSigned-off-by: mayank mayank.patel@mayadata.io