chore(deps): bump github.com/Azure/azure-sdk-for-go/sdk/storage/azblob from 0.4.1 to 1.0.0 #10509
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps [github.com/Azure/azure-sdk-for-go/sdk/storage/azblob](https://github.com/Azure/azure-sdk-for-go) from 0.4.1 to 1.0.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/azcore/v0.4.1...v1.0) --- updated-dependencies: - dependency-name: github.com/Azure/azure-sdk-for-go/sdk/storage/azblob dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
bot
added
type/dependencies
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Merge queue setting changed
|
@dependabot ignore this major version |
|
OK, I won't notify you about version 1.x.x again, unless you re-open this PR. 😢 |
dependabot
bot
deleted the
dependabot/go_modules/github.com/Azure/azure-sdk-for-go/sdk/storage/azblob-1.0.0
branch
|
should this PR be re-openend? last update (#12459) was manually. maybe it can be automatically again? (i don't know the reason why it was disabled/ignored) |
This was properly updated in #11251 as it had breaking changes that needed updating code
Afaict, some maintainers in the past just closed or ignored these PRs when they failed CI, which I don't think is a good approach, especially when there is no reason documented (as you point out and as I have in the past too). We should remove all the manual ignores from messages like these and only keep the explicit ignores in the |
|
2 recent changes:
|
|
@dependabot show * ignore conditions |
|
No ignore conditions found for the dependency * |
|
@dependabot show github.com/Azure/azure-sdk-for-go/sdk/storage/azblob ignore conditions |
Ignore Conditions
|
|
@dependabot unignore github.com/Azure/azure-sdk-for-go/sdk/storage/azblob |
|
Non Grouped Update Pull Requests do not support unignore commands. |
|
Turns out this is somehow impossible to fix in current dependabot 😐 : dependabot/dependabot-core#6489 |
Bumps github.com/Azure/azure-sdk-for-go/sdk/storage/azblob from 0.4.1 to 1.0.0.
Release notes
Sourced from github.com/Azure/azure-sdk-for-go/sdk/storage/azblob's releases.
... (truncated)
Commits
1988e0cAded DeleteDisk method72aed89Added CheckHostedServiceNameAvailability method, fixed minor bugs84da83bUpdate README.md2edf9b0Added parameters validationa870bf1Removed "ResourceNotFound" check from vmClient116b917Added RoleInstance entity to vmClient4f1c2edFormatted entities in clients0adc3f4Removed fingerprint printing from vmClienta1a6933Fixed SendAzureDeleteRequest method3f2caf9Added new VM operationsDependabot 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 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)