forked from confluentinc/confluent-kafka-go
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Bump github.com/Azure/azure-sdk-for-go/sdk/azidentity from 1.5.1 to 1.6.0 #4
Open
dependabot
wants to merge
6
commits into
master
Choose a base branch
from
dependabot/go_modules/github.com/Azure/azure-sdk-for-go/sdk/azidentity-1.6.0
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Bumps [github.com/docker/docker](https://github.com/docker/docker) from 26.1.0+incompatible to 26.1.5+incompatible. - [Release notes](https://github.com/docker/docker/releases) - [Commits](moby/moby@v26.1.0...v26.1.5) --- updated-dependencies: - dependency-name: github.com/docker/docker dependency-type: indirect ... Signed-off-by: dependabot[bot] <[email protected]>
…stToSchemaCache entries Why?: in order to allow refresh the internal state of cache that belongs to, the first time that GetLatestSchemaMetadata method is executed (client#latestToSchemaCache) or when the ttl cache is exired Implementation: - RefreshLatestSchemaMetadataCache method implementation into schemaregistry_client.go, assuimg variadic subjects arguments, iterating it and getting the schema-metadata - by each schema-metadata, when it call occurs and get the schema-metadata into &SchemaMetadata - lock latestToSchemaCacheLock for possible R/W ah update latestToSchemaCache internal-state - when an error occurs when calling schema-metadata obtention, it puts in a multierror and returns the possible errors to be aware about this behaviour
…ocker/docker-26.1.5incompatible Bump github.com/docker/docker from 26.1.0+incompatible to 26.1.5+incompatible
…hemaCache entries RefreshLatestSchemaMetadataCache implementation refreshing latestToSchemaCache entries Issue confluentinc#1274 Why?: in order to allow refresh the internal state of cache that belongs to, the first time that GetLatestSchemaMetadata method is executed (client#latestToSchemaCache) or when the ttl cache is exired Implementation: RefreshLatestSchemaMetadataCache method implementation into schemaregistry_client.go, assuming variadic string with subjects arguments, iterating it and getting the schema-metadata for each one by each schema-metadata, when it call occurs and get the schema-metadata into &SchemaMetadata lock latestToSchemaCacheLock for possible R/W ah update latestToSchemaCache internal-state when an error occurs when calling schema-metadata obtention, it puts in a multierror and returns the possible errors to be aware about this behavior
Bumps [github.com/Azure/azure-sdk-for-go/sdk/azidentity](https://github.com/Azure/azure-sdk-for-go) from 1.5.1 to 1.6.0. - [Release notes](https://github.com/Azure/azure-sdk-for-go/releases) - [Changelog](https://github.com/Azure/azure-sdk-for-go/blob/main/documentation/release.md) - [Commits](Azure/azure-sdk-for-go@sdk/internal/v1.5.1...sdk/azcore/v1.6.0) --- updated-dependencies: - dependency-name: github.com/Azure/azure-sdk-for-go/sdk/azidentity dependency-type: direct:production ... Signed-off-by: dependabot[bot] <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps github.com/Azure/azure-sdk-for-go/sdk/azidentity from 1.5.1 to 1.6.0.
Release notes
Sourced from github.com/Azure/azure-sdk-for-go/sdk/azidentity's releases.
... (truncated)
Commits
36f766d
add sdk/resourcemanager/cosmos/armcosmos live test (#20705)c005ed6
sdk/resourcemanager/network/armnetwork live test (#20331)5fa7df4
add sdk/resourcemanager/compute/armcompute live test (#20048)0d22aed
add sdk/resourcemanager/eventhub/armeventhub live test (#20686)2a8d96d
add sdk/resourcemanager/postgresql/armpostgresql live test (#20685)b2cddab
[Release] sdk/resourcemanager/paloaltonetworksngfw/armpanngfw/0.1.0 (#20437)ed7f3c7
Fix azidentity troubleshooting guide link (#20736)6dfd0cb
[azeventhubs] Fixing checkpoint store race condition (#20727)745d967
pass along the artifact name so we can override it later (#20732)20b4dd8
Update changelog with latest features (#20730)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 rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.