How to version multiple self maintained dependent SDK packages pushed via azure pipeline?
We have multiple components that have SDKs generated and pushed a private package repository during build process. Right now we have all of them in the same version. For example, lets say we have order, payment and shipment component currently on v1.0 and now we make a major change only to shipment component, then we make sure all of them are set as v2.0 even though change is only to one component. All of these packages are in individual repos too. When ever a PR is raised to dev branch, it adds patch version with alpha tag to it. dev to master will have beta tag and only patch version is updated. If need to make major version like in the example all of them need to be on the same major version because package references in our csproj are like '1.0-alpha-*'
1) Is there a better way to handle versioning?
2)Looking at a way to minimize manual intervention?
0 Replies