azure-data-explorer-datasource
azure-data-explorer-datasource copied to clipboard
Bump github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.10.0 to 1.11.1
Bumps github.com/Azure/azure-sdk-for-go/sdk/azcore from 1.10.0 to 1.11.1.
Release notes
Sourced from github.com/Azure/azure-sdk-for-go/sdk/azcore's releases.
sdk/azcore/v1.11.1
1.11.1 (2024-04-02)
Bugs Fixed
- Pollers that use the
Locationheader won't considerhttp.StatusRequestTimeouta terminal failure.runtime.Poller[T].Resultwon't consider non-terminal error responses as terminal.sdk/azcore/v1.11.0
1.11.0 (2024-04-01)
Features Added
- Added
StatusCodestoarm/policy.RegistrationOptionsto allow supporting non-standard HTTP status codes during registration.- Added field
InsecureAllowCredentialWithHTTPtoazcore.ClientOptionsand dependent authentication pipeline policies.- Added type
MultipartContentto thestreamingpackage to support multipart/form payloads with custom Content-Type and file name.Bugs Fixed
runtime.SetMultipartFormDatawon't try to stringify[]bytevalues.- Pollers that use the
Locationheader won't considerhttp.StatusTooManyRequestsa terminal failure.Other Changes
- Update dependencies.
Commits
76e5495Prep [email protected] for release (#22680)2650473Increment package version after release of messaging/azeventhubs (#22677)51ef615runtime.Poller.Result won't be done on non-terminal error (#22675)aef7678Increment package version after release of messaging/azservicebus (#22678)a67b4deIncrement package version after release of messaging/eventgrid/azeventgrid (#...e978d51[azopenai] Updating doc comments based on feedback from an issue, as well as ...4116d5dDon't consider 408 as terminal failure for Location poller (#22674)e036aeaSync eng/common directory with azure-sdk-tools for PR 7989 (#22673)53f73adSync eng/common directory with azure-sdk-tools for PR 7988 (#22672)9e78ee2[azeventgrid] Prepping for first GA of the Event Grid Basic package. (#22667)- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Not approving minor update to a non-allowlisted production dependency
Use the following command to run this PR with Docker at http://localhost:3000:
docker run --rm -p 3000:3000 grafana/plugin-builds:9fd99c45c70b90d8964150955928c06829e587c0pre
Not approving minor update to a non-allowlisted production dependency
@dependabot rebase
Not approving minor update to a non-allowlisted production dependency