Repository navigation
Bump the grouped-dependencies group with 8 updates - #83
Open
dependabot[bot] wants to merge 1 commit into
Open
dependabot[bot] wants to merge 1 commit into
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps coverlet.collector from 10.1.0 to 10.1.1 Bumps Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation from 9.0.20 to 9.0.23 Bumps Microsoft.NET.Test.Sdk from 18.10.1 to 18.12.0 Bumps Microsoft.OpenApi from 3.10.2 to 3.11.0 Bumps SkiaSharp from 4.153.1 to 4.156.1 Bumps Swashbuckle.AspNetCore from 10.2.3 to 11.0.1 Bumps System.Text.Json from 10.0.12 to 11.0.0 Bumps xunit.runner.visualstudio from 4.0.0 to 4.0.1 --- updated-dependencies: - dependency-name: coverlet.collector dependency-version: 10.1.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: grouped-dependencies - dependency-name: Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation dependency-version: 9.0.23 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: grouped-dependencies - dependency-name: Microsoft.NET.Test.Sdk dependency-version: 18.12.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: grouped-dependencies - dependency-name: Microsoft.OpenApi dependency-version: 3.11.0 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: grouped-dependencies - dependency-name: SkiaSharp dependency-version: 4.156.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: grouped-dependencies - dependency-name: SkiaSharp dependency-version: 4.156.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: grouped-dependencies - dependency-name: Swashbuckle.AspNetCore dependency-version: 11.0.1 dependency-type: direct:production update-type: version-update:semver-major dependency-group: grouped-dependencies - dependency-name: System.Text.Json dependency-version: 11.0.0 dependency-type: direct:production update-type: version-update:semver-major dependency-group: grouped-dependencies - dependency-name: xunit.runner.visualstudio dependency-version: 4.0.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: grouped-dependencies ... Signed-off-by: dependabot[bot] <support@github.com>
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.
Updated coverlet.collector from 10.1.0 to 10.1.1.
Release notes
Sourced from coverlet.collector's releases.
10.1.1
Improvements
IsReachableto branch points, computed from the method's control-flow graph, and exclude unreachable branches from branch-coverage totals and from branch details in Cobertura, LCOV and OpenCover reports #2056 by @pcshrosbreeFixed
Maintenance
Diff between 10.1.0 and 10.1.1
Commits viewable in compare view.
Updated Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation from 9.0.20 to 9.0.23.
Release notes
Sourced from Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation's releases.
9.0.23
Release
What's Changed
36ba75ftobc548fdby @dependabot[bot] in [release/9.0] (deps): Bump src/submodules/googletest from36ba75ftobc548fddotnet/aspnetcore#69626365965ftobe938cdby @dependabot[bot] in [release/9.0] (deps): Bump src/submodules/MessagePack-CSharp from365965ftobe938cddotnet/aspnetcore#69536bc548fdtob66cffcby @dependabot[bot] in [release/9.0] (deps): Bump src/submodules/googletest frombc548fdtob66cffcdotnet/aspnetcore#69815Full Changelog: dotnet/aspnetcore@v9.0.21...v9.0.23
9.0.22
Release
Full Changelog: dotnet/aspnetcore@v9.0.21...v9.0.22
9.0.21
Release
What's Changed
3940de9to36ba75fby @dependabot[bot] in [release/9.0] (deps): Bump src/submodules/googletest from3940de9to36ba75fdotnet/aspnetcore#68919Full Changelog: dotnet/aspnetcore@v9.0.20...v9.0.21
Commits viewable in compare view.
Updated Microsoft.NET.Test.Sdk from 18.10.1 to 18.12.0.
Release notes
Sourced from Microsoft.NET.Test.Sdk's releases.
18.12.0
Security fix
This release includes the fix for CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0 and earlier. Every version from 18.11.1 on is fixed, including 18.12.0.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.12.0
18.11.1
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.11.0.Fixed in:
Microsoft.TestPlatform.CLI18.11.1.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.11.0...v18.11.1
18.11.0
What's Changed
New Contributors
Full Changelog: microsoft/vstest@v18.10.1...v18.11.0
18.10.2
Security fix
This release fixes CVE-2026-105544, an elevation of privilege vulnerability in the VSTest artifact post-processor. The post-processor could consume a forged
executionComplete.jsonwritten by another local user, and then run attacker-controlled output handling.Affected:
Microsoft.TestPlatform.CLI18.10.0 and 18.10.1.Fixed in:
Microsoft.TestPlatform.CLI18.10.2.Microsoft.TestPlatform.CLIis the VSTest build that we ship into the .NET SDK. The recommended way to get this fix is to update your .NET SDK to the latest patched version, see the advisory for the SDK versions.The fix is also released in the
Microsoft.TestPlatform.CLIpackage, for completeness. That package is rarely used directly. It is not a dependency ofMicrosoft.NET.Test.SdkorMicrosoft.TestPlatform, so those packages do not bring it in.Details: microsoft/vstest#16654 and dotnet/announcements#517
Using custom Docker images or Nano Server? See microsoft/vstest#16652
What's Changed
Full Changelog: microsoft/vstest@v18.10.1...v18.10.2
Commits viewable in compare view.
Updated Microsoft.OpenApi from 3.10.2 to 3.11.0.
Release notes
Sourced from Microsoft.OpenApi's releases.
3.11.0
3.11.0 (2026-10-19)
Features
Bug Fixes
Commits viewable in compare view.
Updated SkiaSharp from 4.153.1 to 4.156.1.
Updated Swashbuckle.AspNetCore from 10.2.3 to 11.0.1.
Release notes
Sourced from Swashbuckle.AspNetCore's releases.
11.0.1
What's Changed
SubmitMethod.Queryby @martincostello in [SwaggerUI] Add SubmitMethod.Query domaindrivendev/Swashbuckle.AspNetCore#4268Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v11.0.0...v11.0.1
11.0.0
Swashbuckle.AspNetCore v11.0.0
With this release, Swashbuckle.AspNetCore adds support for generating OpenAPI 3.2 documents and for ASP.NET Core 11.
Swashbuckle.AspNetCore v11 depends on OpenAPI.NET v3.11 which introduces some breaking changes to the public API surface. More information can be found in their OpenAPI.NET v3 Upgrade Guide.
To reduce the number of breaking behavioural changes in Swashbuckle.AspNetCore v11, generation of OpenAPI 3.1 and 3.2 documents is opt-in.
To generate OpenAPI 3.1 or 3.2 documents, change the OpenAPI version as shown in the code snippet below:
What's Changed
New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.3.1...v11.0.0
10.3.1
What's Changed
AmbiguousMatchExceptionfor[FromQuery]by @SENESO in Fix AmbiguousMatchException for [FromQuery] domaindrivendev/Swashbuckle.AspNetCore#4209ISerializerDataContractResolverby @DevKaurav-14 in Avoid deadlock when a schema filter depends on ISerializerDataContractResolver domaindrivendev/Swashbuckle.AspNetCore#4210Deprecations
New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.3.0...v10.3.1
10.3.0
What's Changed
anyOf,allOf,oneOfortype = nullby @ldeluigi in Change nullability handling for schemas with anyOf, allOf, oneOf or type = null domaindrivendev/Swashbuckle.AspNetCore#3976AddServeracross multiple documents by @RaphaelFakhri in Add coverage for AddServer across multiple documents domaindrivendev/Swashbuckle.AspNetCore#4115[EnumMember]by @RaphaelFakhri in Document that System.Text.Json ignores [EnumMember] domaindrivendev/Swashbuckle.AspNetCore#4127ConfigObject.AdditionalItemsby @RaphaelFakhri in Fix #3153: serialize custom values in the UI ConfigObject AdditionalItems domaindrivendev/Swashbuckle.AspNetCore#4132New Contributors
Full Changelog: domaindrivendev/Swashbuckle.AspNetCore@v10.2.3...v10.3.0
Commits viewable in compare view.
Updated System.Text.Json from 10.0.12 to 11.0.0.
Release notes
Sourced from System.Text.Json's releases.
10.0.404
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.404and 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
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.404-servicing.26529.119.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archives use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.10.0.403
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.403and 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.402
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.402and 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.401
Release
What's Changed
... (truncated)
10.0.400
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.400and 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.303
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.303and 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.302
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.302and 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.301
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.301and 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.300
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.300and 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.204
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.204and 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.203
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.203and 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.202
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.202and 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.201
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.201and 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.200
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.200and 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.115
You can build .NET 10.0 from the repository by cloning the release tag
v10.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
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.115-servicing.26529.108.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signature was generated from a build-produced source archive with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archive uses0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.10.0.114
You can build .NET 10.0 from the repository by cloning the release tag
v10.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 are PGP signatures for the GitHub generated tarball and zipball. You can find the public key at https://dot.net/release-key-2023
Important
Please use https://builds.dotnet.microsoft.com/dotnet/source-build/dotnet-source-10.0.114-servicing.26522.126.tar.gz instead of the GitHub-generated sources tarball. This is due to a discrepancy in the ownership metadata. The signatures were generated from build-produced source archives with ownership normalized to UID/GID
2001:2001, while GitHub’s automatically generated archives use0:0. The source contents are identical, but the ownership metadata changes the archive bytes, causing signature verification to fail.10.0.113
You can build .NET 10.0 from the repository by cloning the release tag
v10.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
10.0.112
You can build .NET 10.0 from the repository by cloning the release tag
v10.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
10.0.111
You can build .NET 10.0 from the repository by cloning the release tag
v10.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
10.0.110
You can build .NET 10.0 from the repository by cloning the release tag
v10.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
10.0.109
You can build .NET 10.0 from the repository by cloning the release tag
v10.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
10.0.108
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.108and 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.107
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.107and 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.106
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.106and 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.105
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.105and 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.104
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.104and 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.103
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.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 is the PGP signature for the GitHub generated tarball. You can find the public key at https://dot.net/release-key-2023
10.0.102-sb1
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.102-sb1and 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.101
You can build .NET 10.0 from the repository by cloning the release tag
v10.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
10.0.100
You can build .NET 10.0 from the repository by cloning the release tag
v10.0.100and 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
To produce artifacts with the .NET 10 GA version strings, users must pass the branding argument to the build:
--branding rtm.10.0.100-rc.2.25502.107
You can build .NET 10.0 RC 2 from the repository by cloning the release tag
v10.0.100-rc.2.25502.107and 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
Note: GitHub automatically generates the "Source code (tar.gz/zip)" archives included in this release. Please download the official source code from:
10.0.100-rc.1.25451.107
You can build .NET 10.0 RC 1 from the repository by cloning the release tag
v10.0.100-rc.1.25451.107and 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.100-preview.7.25380.108
You can build .NET 10.0 Preview 7 from the repository by cloning the release tag
v10.0.100-preview.7.25380.108and 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 xunit.runner.visualstudio from 4.0.0 to 4.0.1.
Release notes
Sourced from xunit.runner.visualstudio's releases.
4.0.1
Release notes: https://xunit.net/releases/visualstudio/4.0.1
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