-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feb key vault release #4319
Feb key vault release #4319
Conversation
I think we rather should update the core minimum version from "1.5.0" to "1.8.0" in |
sdk/keyvault/azure-security-keyvault-administration/CHANGELOG.md
Outdated
Show resolved
Hide resolved
sdk/keyvault/azure-security-keyvault-administration/CHANGELOG.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Ahson Khan <[email protected]>
but 1.8.0 has not been released, we are also releasing 1.8.0-beta4 , the last GA one is 1.7.2 |
@gearama, we are releasing Core 1.8.0 tomorrow. But sorry for the rather bad suggestion about updating the CMakeLists.txt. But the other two files from the |
sdk/keyvault/azure-security-keyvault-administration/CMakeLists.txt
Outdated
Show resolved
Hide resolved
…nto FebKVRelease
This reverts commit 1e0b612.
* kv release * ds * Update sdk/keyvault/azure-security-keyvault-administration/CHANGELOG.md Co-authored-by: Ahson Khan <[email protected]> * core to latest GA * 1.8.0 * update folder list * put to stable versions * put back to last GA * put back to original * try core 1.8.0 * Revert "try core 1.8.0" This reverts commit 1e0b612. --------- Co-authored-by: Ahson Khan <[email protected]>
Pull Request Checklist
Please leverage this checklist as a reminder to address commonly occurring feedback when submitting a pull request to make sure your PR can be reviewed quickly:
See the detailed list in the contributing guide.