Core Library Upgrades
Type of change
-
Bug Fix -
Feature
Please provide link to gitlab issue or ADR(Architecture Decision Record)
Just Upgrading Core Libraries to the latest stable versions
Does this introduce a change in the core logic?
- [Yes]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
Current we are referring to the older versions of the core-lib-azure and core-common in WKS service while we have had new stable versions for these libraries for some time now.
What is the new/expected behavior?
Upgraded the versions of core-lib-azure and core-common Libraries to latest stable versions(0.7.0 for both) in the entire project
Have you added/updated Unit Tests and Integration Tests?
NA
Any other useful information
Merge request reports
Activity
added M5 label
@devesh @harshit283 @polavishnu Please review and Refer to the description above for the changes
added 3 commits
-
34bca6d7...8820a145 - 2 commits from branch
master
- e8937381 - Merge branch 'master' into abhic-core-lib-Upgrade
-
34bca6d7...8820a145 - 2 commits from branch
- Resolved by Hema Vishnu Pola [Microsoft]
@abhishek - Please use the template for the MR that is in use. Did we run locally and verified all the tests to pass?
enabled an automatic merge when the pipeline for e8937381 succeeds
- Resolved by Abhishek Chowdhry
@abhishek - You would require to update the fossa NOTICE file. Please do the required for this MR.
@polavishnu Can we please close this MR?
enabled an automatic merge when the pipeline for 1cb4cd3d succeeds
enabled an automatic merge when the pipeline for 1cb4cd3d succeeds
mentioned in commit 6f4865fa