Bump Azure.Identity and 11 others#26
Open
dependabot[bot] wants to merge 1 commit into
Open
Conversation
Bumps Azure.Identity from 1.17.1 to 1.21.0 Bumps Azure.Storage.Blobs from 12.24.0 to 12.28.0 Bumps coverlet.collector from 8.0.1 to 10.0.1 Bumps FluentFTP from 51.1.0 to 54.2.0 Bumps Microsoft.ApplicationInsights from 2.23.0 to 3.1.2 Bumps Microsoft.ApplicationInsights.AspNetCore from 2.23.0 to 3.1.2 Bumps Microsoft.ApplicationInsights.Profiler.AspNetCore from 3.0.1 to 3.0.2 Bumps Microsoft.Extensions.Diagnostics.HealthChecks from 9.0.7 to 10.0.8 Bumps Microsoft.Extensions.Hosting from 10.0.5 to 10.0.8 Bumps Microsoft.NET.Test.Sdk from 18.3.0 to 18.6.0 Bumps XtremeIdiots.Portal.Integrations.Servers.Api.Client.V1 from 2.1.164 to 2.1.170 Bumps XtremeIdiots.Portal.Server.Events.Abstractions.V1 from 1.1.19 to 1.1.46 --- updated-dependencies: - dependency-name: Azure.Identity dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: Azure.Storage.Blobs dependency-version: 12.28.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: FluentFTP dependency-version: 54.2.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: Microsoft.ApplicationInsights.AspNetCore dependency-version: 3.1.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: Microsoft.ApplicationInsights.Profiler.AspNetCore dependency-version: 3.0.2 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: Microsoft.Extensions.Diagnostics.HealthChecks dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: Microsoft.Extensions.Hosting dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: XtremeIdiots.Portal.Integrations.Servers.Api.Client.V1 dependency-version: 2.1.170 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: XtremeIdiots.Portal.Server.Events.Abstractions.V1 dependency-version: 1.1.46 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: coverlet.collector dependency-version: 10.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: Microsoft.ApplicationInsights dependency-version: 3.1.2 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: Microsoft.Extensions.Diagnostics.HealthChecks dependency-version: 10.0.8 dependency-type: direct:production update-type: version-update:semver-major dependency-group: nuget - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.6.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: nuget - dependency-name: XtremeIdiots.Portal.Integrations.Servers.Api.Client.V1 dependency-version: 2.1.170 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget - dependency-name: XtremeIdiots.Portal.Server.Events.Abstractions.V1 dependency-version: 1.1.46 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: nuget ... Signed-off-by: dependabot[bot] <support@github.com>
Dependency ReviewThe following issues were found:
License Issuessrc/XtremeIdiots.Portal.Server.Agent.App.Tests/XtremeIdiots.Portal.Server.Agent.App.Tests.csproj
src/XtremeIdiots.Portal.Server.Agent.App/XtremeIdiots.Portal.Server.Agent.App.csproj
OpenSSF ScorecardScorecard details
Scanned Files
|
This file contains hidden or 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
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.
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Updated Azure.Identity from 1.17.1 to 1.21.0.
Release notes
Sourced from Azure.Identity's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Azure.Storage.Blobs from 12.24.0 to 12.28.0.
Release notes
Sourced from Azure.Storage.Blobs's releases.
12.28.0
12.28.0 (2026-05-12)
Features Added
Bugs Fixed
TokenRequestContext.Scopescontained a double slash (e.g.https://storage.azure.com//.default) when usingTokenCredentialauthentication. (#58295)12.27.0
12.27.0 (2026-05-12)
Bugs Fixed
TokenRequestContext.Scopescontained a double slash (e.g.https://storage.azure.com//.default) when usingTokenCredentialauthentication. (#58295)12.26.0
12.26.0 (2026-05-12)
Features Added
Bugs Fixed
TokenRequestContext.Scopescontained a double slash (e.g.https://storage.azure.com//.default) when usingTokenCredentialauthentication. (#58295)12.25.0
12.25.0 (2026-05-12)
Features Added
Commits viewable in compare view.
Updated coverlet.collector from 8.0.1 to 10.0.1.
Release notes
Sourced from coverlet.collector's releases.
10.0.1
Improvements
Fixed
Maintenance
Diff between 10.0.0 and 10.0.1
10.0.0
Improvements
--coverlet-file-prefixoption for unique report files #1869Fixed
Maintenance
Diff between 8.0.1 and 10.0.0
Commits viewable in compare view.
Updated FluentFTP from 51.1.0 to 54.2.0.
Release notes
Sourced from FluentFTP's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.ApplicationInsights from 2.23.0 to 3.1.2.
Release notes
Sourced from Microsoft.ApplicationInsights's releases.
3.1.2
Version 3.1.2
HttpException: Request is not available in this contextin the WEB package when callingTrackDependencyfromApplication_Startin classic ASP.NET. The WEB activity processors now safely handle the case whereHttpContext.Requestis not yet available.TelemetryConfiguration.CreateDefault()on classic ASP.NET now returns a configuration already populated fromApplicationInsights.config(connection string, sampling, storage, live metrics, request/dependency tracking, etc.). A newPreApplicationStartMethod(WebApplicationInsightsInitializer) materializes and populates the singleton beforeApplication_Startruns, so customer code callingTelemetryConfiguration.CreateDefault()fromGlobal.asax.csno longer gets an empty configuration. TheApplicationInsightsHttpModuleno longer carries the config-reading bookkeeping.TelemetryConfiguration.PrependOpenTelemetryBuilderConfigurationno longer throws if the configuration was already built — it silently skips, so a secondTelemetryClientconstructed against an already-built configuration no longer throwsInvalidOperationException.3.1.1
Version 3.1.1
OpenTelemetry.Api1.15.1): Update OpenTelemetry and Azure Monitor packages to address vulnerabilities microsoft/ApplicationInsights-dotnet#31743.1.0
Version 3.1.0
TelemetryContextproperties public and propagate them viaTelemetryClient.APPLICATIONINSIGHTS_CONNECTION_STRINGenvironment variable for Base, Web, and NLog packages when connection string is not set via code.OTEL_SDK_DISABLEDnot being honored whenTelemetryConfiguration.DisableTelemetryis set in DI scenarios., #3157TrackAvailabilityignoring user-specifiedTimestamponAvailabilityTelemetry. The timestamp is now emitted asmicrosoft.availability.testTimestampso downstream exporters can use the correct event time.netstandard2.0target framework toMicrosoft.ApplicationInsightspackage to support customers with shared libraries targeting netstandard2.0.TelemetryClient.Context.Cloud.RoleNameset after construction now applies to all telemetry.NullReferenceExceptioninTelemetryClient.Flush()andFlushAsync()when called from DI scenariosApplicationVersionignored:ApplicationInsightsServiceOptions.ApplicationVersionis now applied asservice.versionon the OpenTelemetry Resource for both AspNetCore and WorkerService packagesHttpRequestExtensions.UnvalidatedGetHeaderalways returning empty string instead of the actual header value. Restored max-length enforcement to guard against oversized header values.3.0.0
netstandard2.0withnet8.0target framework inMicrosoft.ApplicationInsights.NLogTargetpackage.3.0.0-rc1
netstandard2.0target framework fromMicrosoft.ApplicationInsights,Microsoft.ApplicationInsights.AspNetCore, andMicrosoft.ApplicationInsights.WorkerServicepackages.Microsoft.ApplicationInsights.AspNetCorehas been updated to version 10.EnabledAdaptiveSamplingand replaced withTracesPerSecondandSamplingRatioEnableTraceBasedLogsSamplerproperty toApplicationInsightsServiceOptionsfor ASP.NET Core and WorkerService packagesStorageDirectoryandDisableOfflineStoragefromTelemetryConfigurationin DI scenarios3.0.0-beta2
Added
Bug fix
3.0.0-beta1
Commits viewable in compare view.
Updated Microsoft.ApplicationInsights.AspNetCore from 2.23.0 to 3.1.2.
Release notes
Sourced from Microsoft.ApplicationInsights.AspNetCore's releases.
3.1.2
Version 3.1.2
HttpException: Request is not available in this contextin the WEB package when callingTrackDependencyfromApplication_Startin classic ASP.NET. The WEB activity processors now safely handle the case whereHttpContext.Requestis not yet available.TelemetryConfiguration.CreateDefault()on classic ASP.NET now returns a configuration already populated fromApplicationInsights.config(connection string, sampling, storage, live metrics, request/dependency tracking, etc.). A newPreApplicationStartMethod(WebApplicationInsightsInitializer) materializes and populates the singleton beforeApplication_Startruns, so customer code callingTelemetryConfiguration.CreateDefault()fromGlobal.asax.csno longer gets an empty configuration. TheApplicationInsightsHttpModuleno longer carries the config-reading bookkeeping.TelemetryConfiguration.PrependOpenTelemetryBuilderConfigurationno longer throws if the configuration was already built — it silently skips, so a secondTelemetryClientconstructed against an already-built configuration no longer throwsInvalidOperationException.3.1.1
Version 3.1.1
OpenTelemetry.Api1.15.1): Update OpenTelemetry and Azure Monitor packages to address vulnerabilities microsoft/ApplicationInsights-dotnet#31743.1.0
Version 3.1.0
TelemetryContextproperties public and propagate them viaTelemetryClient.APPLICATIONINSIGHTS_CONNECTION_STRINGenvironment variable for Base, Web, and NLog packages when connection string is not set via code.OTEL_SDK_DISABLEDnot being honored whenTelemetryConfiguration.DisableTelemetryis set in DI scenarios., #3157TrackAvailabilityignoring user-specifiedTimestamponAvailabilityTelemetry. The timestamp is now emitted asmicrosoft.availability.testTimestampso downstream exporters can use the correct event time.netstandard2.0target framework toMicrosoft.ApplicationInsightspackage to support customers with shared libraries targeting netstandard2.0.TelemetryClient.Context.Cloud.RoleNameset after construction now applies to all telemetry.NullReferenceExceptioninTelemetryClient.Flush()andFlushAsync()when called from DI scenariosApplicationVersionignored:ApplicationInsightsServiceOptions.ApplicationVersionis now applied asservice.versionon the OpenTelemetry Resource for both AspNetCore and WorkerService packagesHttpRequestExtensions.UnvalidatedGetHeaderalways returning empty string instead of the actual header value. Restored max-length enforcement to guard against oversized header values.3.0.0
netstandard2.0withnet8.0target framework inMicrosoft.ApplicationInsights.NLogTargetpackage.3.0.0-rc1
netstandard2.0target framework fromMicrosoft.ApplicationInsights,Microsoft.ApplicationInsights.AspNetCore, andMicrosoft.ApplicationInsights.WorkerServicepackages.Microsoft.ApplicationInsights.AspNetCorehas been updated to version 10.EnabledAdaptiveSamplingand replaced withTracesPerSecondandSamplingRatioEnableTraceBasedLogsSamplerproperty toApplicationInsightsServiceOptionsfor ASP.NET Core and WorkerService packagesStorageDirectoryandDisableOfflineStoragefromTelemetryConfigurationin DI scenarios3.0.0-beta2
Added
Bug fix
3.0.0-beta1
Commits viewable in compare view.
Updated Microsoft.ApplicationInsights.Profiler.AspNetCore from 3.0.1 to 3.0.2.
Updated Microsoft.Extensions.Diagnostics.HealthChecks from 9.0.7 to 10.0.8.
Release notes
Sourced from Microsoft.Extensions.Diagnostics.HealthChecks's releases.
10.0.0-preview.6.25358.103
You can build .NET 10.0 Preview 6 from the repository by cloning the release tag
v10.0.0-preview.6.25358.103and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.5.25277.114
You can build .NET 10.0 Preview 5 from the repository by cloning the release tag
v10.0.0-preview.5.25277.114and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.4.25258.110
You can build .NET 10.0 Preview 4 from the repository by cloning the release tag
v10.0.0-preview.4.25258.110and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.3.25171.5
You can build .NET 10.0 Preview 3 from the repository by cloning the release tag
v10.0.0-preview.3.25171.5and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.2.25163.2
You can build .NET 10.0 Preview 2 from the repository by cloning the release tag
v10.0.0-preview.2.25163.2and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
10.0.0-preview.1.25080.5
You can build .NET 10.0 Preview 1 from the repository by cloning the release tag
v10.0.0-preview.1.25080.5and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.117
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.117and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.116
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.116and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.115
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.115and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.114
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.114and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023
9.0.113
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.113and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.112
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.112and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.111
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.111and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.110
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.110and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.109
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.109and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
9.0.101
You can build .NET 9.0 from the repository by cloning the release tag
v9.0.101and following the build instructions in the main README.md.Alternatively, you can build from the sources attached to this release directly.
More information on this process can be found in the dotnet/dotnet repository.
Attached are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Commits viewable in compare view.
Updated Microsoft.Extensions.Hosting from 10.0.5 to 10.0.8.
Release notes
Sourced from Microsoft.Extensions.Hosting's releases.
No release notes found for this version range.
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.3.0 to 18.6.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.6.0
What's Changed
Changes to tests and infra
... (truncated)
18.5.1
What's Changed
Full Changelog: microsoft/vstest@v18.5.0...v18.5.1
18.5.0
What's Changed
Full Changelog: microsoft/vstest@v18.4.0...v18.5.0
18.4.0
What's Changed
Add LoongArch64 support by @stdmnpkg in Add LoongArch64 support microsoft/vstest#15359
Refactor Condition evaluation by @Youssef1313 in Refactor Condition evaluation microsoft/vstest#15357
Adding info on extensions points part 1 by @nohwnd in Adding info on extensions points part 1 microsoft/vstest#15360
Add option to ask for uploading code QL before the standard window ends by @nohwnd in Add option to ask for uploading code QL before the standard window ends microsoft/vstest#15373
Update runtime versions by @nohwnd in Update runtime versions microsoft/vstest#15372
Fix .NET 10 regression for traits by @Youssef1313 in Fix .NET 10 regression for traits microsoft/vstest#15370
Update target frameworks to net10.0 and net11.0 by @dotnet-maestro[bot] in Update target frameworks to net10.0 and net11.0 microsoft/vstest#15349
Fix names in pipeline matrix so we don't have to align them by @nohwnd in Fix names in pipeline matrix so we don't have to align them microsoft/vstest#15365
Update SECURITY.md by @Youssef1313 in Update SECURITY.md microsoft/vstest#15342
New Contributors
Full Changelog: microsoft/vstest@v18.3.0...v18.4.0
Commits viewable in compare view.
Updated XtremeIdiots.Portal.Integrations.Servers.Api.Client.V1 from 2.1.164 to 2.1.170.
Release notes
Sourced from XtremeIdiots.Portal.Integrations.Servers.Api.Client.V1's releases.
2.1.170
What's Changed
Full Changelog: frasermolyneux/portal-servers-integration@v2.1.164...v2.1.170
Commits viewable in compare view.
Updated XtremeIdiots.Portal.Server.Events.Abstractions.V1 from 1.1.19 to 1.1.46.
Release notes
Sourced from XtremeIdiots.Portal.Server.Events.Abstractions.V1's releases.
1.1.46
What's Changed
Full Changelog: frasermolyneux/portal-server-events@v1.1.37...v1.1.46
1.1.37
What's Changed
Full Changelog: frasermolyneux/portal-server-events@v1.1.34...v1.1.37
1.1.34
What's Changed
Full Changelog: frasermolyneux/portal-server-events@v1.1.32...v1.1.34
1.1.32
Full Changelog: frasermolyneux/portal-server-events@v1.1.31...v1.1.32
1.1.31
Full Changelog: frasermolyneux/portal-server-events@v1.1.30...v1.1.31
1.1.30
Full Changelog: frasermolyneux/portal-server-events@v1.1.29...v1.1.30
1.1.29
Full Changelog: frasermolyneux/portal-server-events@v1.1.28...v1.1.29
1.1.28
Full Changelog: frasermolyneux/portal-server-events@v1.1.27...v1.1.28
1.1.27
What's Changed
Full Changelog: frasermolyneux/portal-server-events@v1.1.25...v1.1.27
1.1.25
Full Changelog: frasermolyneux/portal-server-events@v1.1.24...v1.1.25
1.1.24
Full Changelog: frasermolyneux/portal-server-events@v1.1.23...v1.1.24
1.1.23
Full Changelog: frasermolyneux/portal-server-events@v1.1.22...v1.1.23
1.1.22
Full Changelog: frasermolyneux/portal-server-events@v1.1.21...v1.1.22
1.1.21
Full Changelog: frasermolyneux/portal-server-events@v1.1.20...v1.1.21
1.1.20
Full Changelog: frasermolyneux/portal-server-events@v1.1.19...v1.1.20
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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions