Skip to content
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

Prep for independent release; update deps #101

Merged
merged 2 commits into from
Mar 28, 2023
Merged

Conversation

swenson
Copy link
Contributor

@swenson swenson commented Mar 27, 2023

We had to update the API version since the 2018 preview API was dropped in the latest Azure SDK.

We had to update the API version since the 2018 preview API
was dropped in the latest Azure SDK.
@swenson swenson requested a review from a team March 27, 2023 18:18
Comment on lines +10 to +12
* `github.com/Azure/azure-sdk-for-go` v67.2.0+incompatible -> v68.0.0+incompatible
* `github.com/Azure/azure-sdk-for-go/sdk/azcore` v1.3.1 -> v1.4.0
* `github.com/Azure/azure-sdk-for-go/sdk/azidentity` v1.2.1 -> v1.2.2
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These dep updates going into a patch release worry me a bit while this plugin is bundled with Vault. Since v0.13.0 of this plugin has already been bundled into Vault 1.13, I wonder if these dep updates warrant a minor version increment of the plugin instead? (i.e. v0.14.0 instead of v0.13.1)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No problem. I'm happy to do a minor release.

@swenson
Copy link
Contributor Author

swenson commented Mar 28, 2023

Thanks!

@swenson swenson merged commit 2e95dda into main Mar 28, 2023
@swenson swenson deleted the vault-9367/prep-for-release branch March 28, 2023 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants