[dependabot]

Bumps the gradle-dependencies group with 17 updates in the / directory:

Package	From	To
gradle-wrapper	9.6.1	9.8.2
androidx.datastore:datastore-preferences	1.2.1	1.3.0
androidx.appcompat:appcompat	1.7.1	1.8.0
androidx.compose:compose-bom	2026.06.01	2026.09.00
androidx.core:core-ktx	1.19.0	1.19.1
com.google.firebase:firebase-bom	34.17.0	35.1.0
com.google.android.gms:play-services-oss-licenses	17.5.1	17.5.3
org.jetbrains.kotlinx:kotlinx-serialization-json	1.11.0	1.12.0
com.squareup.okhttp3:logging-interceptor	5.4.0	5.5.1
com.squareup.okhttp3:mockwebserver	5.4.0	5.5.1
com.google.maps.android:maps-compose	8.4.0	9.0.1
com.google.android.gms:play-services-maps	20.0.0	20.1.0
androidx.work:work-runtime-ktx	2.11.2	2.12.0
com.android.application	9.3.1	9.5.0
com.google.devtools.ksp	2.3.10	2.3.12
org.jetbrains.kotlin.plugin.compose	2.4.10	2.4.21
org.jetbrains.kotlin.plugin.serialization	2.4.10	2.4.21
org.jetbrains.kotlin.plugin.serialization	2.4.10	2.4.21

Updates gradle-wrapper from 9.6.1 to 9.8.2

Release notes

Sourced from gradle-wrapper's releases.

9.8.2

The Gradle team is excited to announce Gradle 9.8.2.

Here are the highlights of this release:

• Java 27 support
• Maven mirror settings reuse
• Linked problem locations in build output

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle: Aman Gautam, Björn Kautler, Eng Zer Jun, Hashim Khan, Julian Krannich, KBS, Labh R Jethe, Mark Dodgson, Maxim, monkey, nataphon-ktsystems, Paul King, Qiu Tian, rg_sandesh, Roberto Perez Alcolea, Sean, Zongle Wang.

Upgrade instructions

Switch your build to use Gradle 9.8.2 by updating your wrapper:

./gradlew :wrapper --gradle-version=9.8.2 && ./gradlew :wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

9.8.1

This is a patch release for Gradle 9.8.0. We recommend using 9.8.1 instead of 9.8.0.

This release addresses three high rated vulnerabilities:

... (truncated)

Commits

• 8de7bcf Speed up the AllVersionsCrossVersion flaky quarantine (#39494)
• 66805db Run all cross-version targets in flaky quarantine
• cdd4c8f Skip empty test tasks in the flaky test quarantine
• 6badb77 Split the AllVersionsCrossVersion quarantine across agents
• 1655e44 Prepare for 9.8.2 (#39492)
• 6702214 Prepare for 9.8.2
• 688c0c1 Fix false warning about unstable graph (#39479)
• 3601d4f Clarify selector reuse comments in SelectorState
• 6e836fd Fix false warning about unstable graph
• a0790e5 Fix hidden artifact cleanup pattern in CheckProject (#39451)
• Additional commits viewable in compare view

Updates androidx.datastore:datastore-preferences from 1.2.1 to 1.3.0

Updates androidx.appcompat:appcompat from 1.7.1 to 1.8.0

Updates androidx.compose:compose-bom from 2026.06.01 to 2026.09.00

Updates androidx.core:core-ktx from 1.19.0 to 1.19.1

Updates com.google.firebase:firebase-bom from 34.17.0 to 35.1.0

Updates com.google.android.gms:play-services-oss-licenses from 17.5.1 to 17.5.3

Updates org.jetbrains.kotlinx:kotlinx-serialization-json from 1.11.0 to 1.12.0

Release notes

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's releases.

v1.12.0

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see #3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

The others include:

• Encode unsigned integer types as positive integers (#3194) (thanks to Eyüp Can Akman)
• Correctly decode CborLabel values (#3195)
• Include actual tag info into CborDecodingException (#3197)

Protobuf improvements

Protocol buffers format received a big new feature: support for unknown fields. Using a new ProtoUnknownFieldHolder class, you can now decode and store unknown fields in Protobuf messages to retransmit them back later. See documentation updates and #2860 for details.

... (truncated)

Changelog

Sourced from org.jetbrains.kotlinx:kotlinx-serialization-json's changelog.

1.12.0 / 2026-10-19

This release is based on Kotlin 2.4.10 and contains all of the changes from 1.12.0-RC.

Additionally, it includes a fix removing unnecessary leading whitespaces from Proguard rules (#3270), and two changes stabilizing kotlin.uuid.Uuid serializer (#3263) and kotlin.time.Instant serializers (#3261).

For your convenience, the changelog for 1.12.0-RC is duplicated below:

API stabilization and deprecations

A big portion of the Json and Core APIs has been stabilized. Most important ones include: @KeepGeneratedSerializer and @SerialInfo annotations, JsonNamingStrategy, and ContextualSerializer. Additionally, various descriptor builders such as listDescriptor and JsonElementBuilder's addAll functions are also stable and can be freely used. There is also one deprecation: ChunkedDecoder interface. Since there is no demand for it, we plan to remove it in the future. See details in the #3238, #3239, and #3216.

Also, kotlin.time.Instant and kotlin.uuid.Uuid serializers are no longer annotated with experimental annotations from the Kotlin standard library (see [#3261](Kotlin/kotlinx.serialization#3261 and #3263)

Performance improvements

We also improved performance in various areas. ASCII-specific parser (#3225) brings performance of decoding from Okio and kotlinx-io sources closer to decoding performance from String. #3220 makes decoding significantly faster in case JsonElement present in your serializable classes. And #3248 should bring overall performance improvements (up to 30%) on large strings.

Exceptions rework

We continue to improve exception handling in Json encoders and decoders. #3235 makes a big change around custom serializers and @Serializable classes constructors: from now on, every exception thrown during deserialization is wrapped by decoder into a JsonException. This way, it is more predictable to write a catch and it is easier to understand what went wrong: JsonDecodingException also includes context information such as Json path and input. Besides that, #3246 limits maximum nesting depth of Json document, so you will get a proper JsonDecodingException instead of a random stack overflow error.

CBOR improvements

CBOR format also gets many improvements in this release. The most important one is memory optimization for definitely-sized collections (#3191, #3192).

... (truncated)

Commits

• 4c28c3e 1.12.0 release (#3295)
• abe8a96 Merge remote-tracking branch 'origin/master' into dev
• 952d17a Added Gradle task to prepare release (#3279)
• 6f30025 Remove Play verification files (#3266)
• 89b23ca Workaround watchosArm32 removal (#3291)
• 53932a0 Update links to Okio site and its docs (#3292)
• 3a5db3b Reduce the number of input fields for bug report
• 9ede0e2 Added templates to the issue creation wizard
• 5d3f884 Update Dokka to version 2.3.0-Beta (#3286)
• 1fe9a49 Suppress deprecation of nodejs in wasmWasi configuration (#3287)
• Additional commits viewable in compare view

Updates com.squareup.okhttp3:logging-interceptor from 5.4.0 to 5.5.1

Changelog

Sourced from com.squareup.okhttp3:logging-interceptor's changelog.

Version 5.5.1

2026_10_22

• Fix: [Block 8 compromised eMudhra intermediate certificates][Mozilla_eMudhra]. Note that this update is not necessary for Android devices with Google Play Services as Google has issued an [automatic update][Google_eMudhra]. This change protects JVMs and AOSP devices that are exposed to the compromised certificates.

Version 5.5.0

2026-08-16

This release introduces opt-in support for [Encrypted Client Hello (ECH)]. This new feature improves user privacy by encrypting domain names in transit. With regular TLS, your coffee shop’s Wi-Fi router can see that you’re visiting wikipedia.com, but it cannot see which page you’re looking at. With ECH, the router observes only the IP address. This additional privacy is most effective on sites hosted by big CDNs because the IP address doesn’t imply a particular website.

This requires ECH support in the platform’s TLS stack. Today this is only Android 17 (API 37, released June 2026). When other TLS stacks add ECH support, we'll integrate them.

ECH took a lot of work to implement because the encryption keys are published over DNS in the [HTTPS resource record], and we needed to write new code to fetch these records. This release includes a major update to OkHttp’s DNS API: it now supports multiple resource record types (not just IP addresses!), asynchronous streaming results, and in-memory caching.

To opt in, you can use DnsOverHttps:

// DnsOverHttps itself uses OkHttpClient. Build both clients upon the
// same bootstrap client so they share a connection pool and dispatcher.
val bootstrapClient = OkHttpClient()
// This sample uses Cloudflare's 1.1.1.1 DnsOverHttps service.
val client = bootstrapClient.newBuilder()
.dns(DnsOverHttps.Builder()
.client(bootstrapClient)
.url("https://1.1.1.1/dns-query".toHttpUrl())
.build())
.build()

You could also opt in with our new AndroidDns API. Unfortunately, the privacy benefits of ECH are thwarted because its DNS queries are not encrypted by default.

// AndroidDns fetches the HTTPS DNS resource records necessary for ECH.
val client = OkHttpClient.Builder()
</tr></table> 

... (truncated)

Commits

• be5151a Prepare for release 5.5.1.
• 6db9802 OkHttp 5.5.x: Blocklist 8 certificates for CVE-2026-111943 (#9805)
• a94bdf1 Prepare for release 5.5.0.
• ecc3b05 Use a fixed size for DoH request body (#9687)
• 9926082 Revert "Use a fixed size for DoH request body" (#9686)
• 0070c2e Use a fixed size for DoH request body
• 1576453 Order ServiceMetadata records per the spec (#9683)
• fb582e9 Flip wiring of Dns.SYSTEM (#9682)
• 4e884ab retryOnConnectionFailure doesn't impact ECH retries (#9681)
• 0433cee Only one contributing.md doc (#9678)
• Additional commits viewable in compare view

Updates com.squareup.okhttp3:mockwebserver from 5.4.0 to 5.5.1

Changelog

Sourced from com.squareup.okhttp3:mockwebserver's changelog.

Version 5.5.1

2026_10_22

• Fix: [Block 8 compromised eMudhra intermediate certificates][Mozilla_eMudhra]. Note that this update is not necessary for Android devices with Google Play Services as Google has issued an [automatic update][Google_eMudhra]. This change protects JVMs and AOSP devices that are exposed to the compromised certificates.

Version 5.5.0

2026-08-16

This release introduces opt-in support for [Encrypted Client Hello (ECH)]. This new feature improves user privacy by encrypting domain names in transit. With regular TLS, your coffee shop’s Wi-Fi router can see that you’re visiting wikipedia.com, but it cannot see which page you’re looking at. With ECH, the router observes only the IP address. This additional privacy is most effective on sites hosted by big CDNs because the IP address doesn’t imply a particular website.

This requires ECH support in the platform’s TLS stack. Today this is only Android 17 (API 37, released June 2026). When other TLS stacks add ECH support, we'll integrate them.

ECH took a lot of work to implement because the encryption keys are published over DNS in the [HTTPS resource record], and we needed to write new code to fetch these records. This release includes a major update to OkHttp’s DNS API: it now supports multiple resource record types (not just IP addresses!), asynchronous streaming results, and in-memory caching.

To opt in, you can use DnsOverHttps:

// DnsOverHttps itself uses OkHttpClient. Build both clients upon the
// same bootstrap client so they share a connection pool and dispatcher.
val bootstrapClient = OkHttpClient()
// This sample uses Cloudflare's 1.1.1.1 DnsOverHttps service.
val client = bootstrapClient.newBuilder()
.dns(DnsOverHttps.Builder()
.client(bootstrapClient)
.url("https://1.1.1.1/dns-query".toHttpUrl())
.build())
.build()

You could also opt in with our new AndroidDns API. Unfortunately, the privacy benefits of ECH are thwarted because its DNS queries are not encrypted by default.

// AndroidDns fetches the HTTPS DNS resource records necessary for ECH.
val client = OkHttpClient.Builder()
</tr></table> 

... (truncated)

Commits

• be5151a Prepare for release 5.5.1.
• 6db9802 OkHttp 5.5.x: Blocklist 8 certificates for CVE-2026-111943 (#9805)
• a94bdf1 Prepare for release 5.5.0.
• ecc3b05 Use a fixed size for DoH request body (#9687)
• 9926082 Revert "Use a fixed size for DoH request body" (#9686)
• 0070c2e Use a fixed size for DoH request body
• 1576453 Order ServiceMetadata records per the spec (#9683)
• fb582e9 Flip wiring of Dns.SYSTEM (#9682)
• 4e884ab retryOnConnectionFailure doesn't impact ECH retries (#9681)
• 0433cee Only one contributing.md doc (#9678)
• Additional commits viewable in compare view

Updates com.google.maps.android:maps-compose from 8.4.0 to 9.0.1

Release notes

Sourced from com.google.maps.android:maps-compose's releases.

v9.0.1

9.0.1 (2026-10-08)

Bug Fixes

• maps-compose: do not apply mapColorScheme to Lite mode maps (#1029) (114aaa5)

v9.0.0

9.0.0 (2026-10-01)

⚠ BREAKING CHANGES

• migrate from android-maps-ktx to android-maps-utils (v9.0.0) (#1002)

Features

• ci: publish an instrumented coverage badge (#1009) (b0d6420)
• migrate from android-maps-ktx to android-maps-utils (v9.0.0) (#1002) (0c49e8d)

v9.0.0-rc03

What's Changed

• sample(maps-app): follow system theme in LiteModeActivity and add documentation guide by @​dkhawk in googlemaps/android-maps-compose#989
• chore(ci): harden Gemini issue triage against prompt injection by @​kikoso in googlemaps/android-maps-compose#992
• docs: add AGENTS.md guidance for AI coding agents by @​kikoso in googlemaps/android-maps-compose#993
• build: migrate unit test coverage from JaCoCo to Kover by @​kikoso in googlemaps/android-maps-compose#994
• ci: record unit and instrumentation test coverage history by @​kikoso in googlemaps/android-maps-compose#1000

Full Changelog: googlemaps/android-maps-compose@v8.6.0...v9.0.0-rc03

v9.0.0-rc02

Full Changelog: googlemaps/android-maps-compose@v8.6.0...v9.0.0-rc02

v9.0.0-rc01

What's Changed

• fix: rename InvalidatingComposeView getRotation param to avoid View shadowing by @​kikoso in googlemaps/android-maps-compose#952
• build(deps): update dependencies, fix zizmor findings, and restore JaCoCo coverage by @​kikoso in googlemaps/android-maps-compose#954
• fix: avoid re-parenting crash for MarkerInfoWindowContent/MarkerInfoWindowComposable by @​kikoso in googlemaps/android-maps-compose#953

Full Changelog: googlemaps/android-maps-compose@v8.4.0...v9.0.0-rc01

v8.6.0

8.6.0 (2026-09-03)

Features

... (truncated)

Changelog

Sourced from com.google.maps.android:maps-compose's changelog.

9.0.1 (2026-10-08)

Bug Fixes

• maps-compose: do not apply mapColorScheme to Lite mode maps (#1029) (114aaa5)

9.0.0 (2026-10-01)

⚠ BREAKING CHANGES

• migrate from android-maps-ktx to android-maps-utils (v9.0.0) (#1002)

Features

• ci: publish an instrumented coverage badge (#1009) (b0d6420)
• migrate from android-maps-ktx to android-maps-utils (v9.0.0) (#1002) (0c49e8d)

8.6.0 (2026-09-03)

Features

• expose map zoom limits (#949) (e0d4572)
• maps-compose: default mapColorScheme to FOLLOW_SYSTEM in GoogleMap (#986) (5f1d438)

Bug Fixes

• guard against null in StreetView panorama change listeners (#970) (6147f75)
• maps-compose: apply mapColorScheme to GoogleMapOptions during MapView creation (#976) (7dec2b7)
• pin ViewTreeLifecycleOwner/SavedStateRegistryOwner on MapView to prevent info window crash (#972) (4024515)

8.5.0 (2026-08-17)

Features

• expose info window customization for advanced markers (#965) (4c65f8c)

Bug Fixes

• avoid re-parenting crash for MarkerInfoWindowContent/MarkerInfoWindowComposable (#953) (12f35a4)
• avoid zero-size crash in rememberComposeBitmapDescriptor when used inside Clustering (#963) (11a2430)
• rename InvalidatingComposeView getRotation param to avoid View shadowing (#952) (1d971cd)

Commits

• 2d380c8 chore(main): release 9.0.1 (#1033)
• cb74115 chore(deps): bump org.jetbrains.kotlinx:kover-gradle-plugin (#1031)
• 8af2400 chore(build): remove foojay toolchain resolver (#1030)
• 622d2f4 docs: explain BEGIN_COMMIT_OVERRIDE for PRs with several changes (#1025)
• 114aaa5 fix(maps-compose): do not apply mapColorScheme to Lite mode maps (#1029)
• 43eff64 chore(deps): bump github/codeql-action/upload-sarif (#1021)
• 6597744 chore(deps): bump the gradle-minor-and-patch group across 1 directory with 12...
• 597c8db test: report instrumentation coverage of the library modules (#1023)
• 61c3cf0 ci: compare unit coverage against the coverage-history branch (#1024)
• 150efd5 chore(main): release 9.0.0 (#1014)
• Additional commits viewable in compare view

Updates com.google.android.gms:play-services-maps from 20.0.0 to 20.1.0

Updates androidx.work:work-runtime-ktx from 2.11.2 to 2.12.0

Updates com.android.application from 9.3.1 to 9.5.0

Updates com.google.devtools.ksp from 2.3.10 to 2.3.12

Release notes

Sourced from com.google.devtools.ksp's releases.

2.3.12

What's Changed

Migrating Processors to Support Backing Fields

This release introduces support for explicit backing fields (#2873), which may now be returned by Resolver.getSymbolsWithAnnotation. To prevent breaking existing processors, new language features require an explicit opt-in.

More generally, the KSP API now explicitly models backing fields for properties. The following is an exhaustive list of functions in KSP API where processor may observe the change after opting in:

• Resolver.getSymbolsWithAnnotation: The function now returns a KSBackingField if the given annotation targeted a field. Previously, if a field were targeted, the function would return a KSProperty.
• Resolver.effectiveJavaModifiers: The function returns fewer modifiers for a KSPropertyDeclaration if it has a backing field, since most of the JVM-specific annotations apply to the backing field. If you are interested in the JVM modifiers, you should call the function with the KSBackingField obtained from the property instead.

Additionally, KSP now models Java fields as properties that always have backing fields. Some of the modifiers now apply to the backing field instead.

Processors adapting to new features must opt in via both of the following steps simultaneously (failing to do both may lead to undefined behavior):

1. The processor should call the registerProcessorForNewFeatures function in SymbolProcessorEnvironment immediately when created (and only once). Example: AbstractTestProcessor.kt#L30
2. All implementations of KSVisitor should move to KSVisitorNext. If their processor code does not directly implement the interface but instead extends one of the KSP-provided visitors (such as KSTopDownVisitor), they should instead extend KSTopDownVisitor(enableNewFeatures = true) and override visitBackingField depending on their code and needs.

Let us know if you run into unexpected behavior!

Bug Fixes

• Fix Resolver.getDeclarationsFromPackage returning incomplete declarations from KLibs in Kotlin Multiplatform (#2396)
• Fix KSP CLI process hanging indefinitely when a processor throws an unhandled exception (#3120)
• Fix implicit task dependency error between KSP and Android Lint in Android KMP (#3128)
• Fix NullPointerException by registering PluginProblemReporter as an application service (#3140)
• Do not mark companion objects as JAVA_STATIC in Resolver.effectiveJavaModifiers (#3125)
• Fix JAVA_STATIC modifier resolution for @​JvmStatic members in Resolver.effectiveJavaModifiers (#3124)
• Update minimum supported Android Gradle Plugin (AGP) version to 8.12.0 (#3149)

New Contributors

Thanks to @​KlyneChrysler, @​budindepunk, and everyone who reported bugs and participated in discussions!

Full Changelog: google/ksp@2.3.11...2.3.12

2.3.11

What's Changed

• Support org.gradle.isolated-projects for project isolation (#3051)
• Fix premature kspDebugAndroidTest task skipping on Android library modules (#3050)
• Fix missing parent declaration exception for @NotNull annotations during incremental compilation (#3030)
• Clean output directories instead of skipping tasks when processor classpath transitions to empty (#3046)
• Fix build cache misses by marking KspGradleConfig.logLevel as @Internal (#3039)
• Add org.gradle.isolated-projects=true to KSP Gradle properties reference table (#3076)
• Add KSP Gradle properties reference table to README documentation (#3070)
• Document collection values in KSValueArgument.value (#3069)
• Update error messaging for ksp.useKSP2 deprecation notice (#3066)

Contributors

• Thanks to @​simonlebras, @​ChristianKatzmann, @​Yong-yuan-X, @​bacecek, @​KlyneChrysler, @​Shaurya2k06, and everyone who reported bugs and participated in discussions!

Full Changelog: google/ksp@2.3.10...2.3.11

Commits

• a3c3859 Format Resolver file
• a614317 Fix grammatical errors in Resolver doc comments
• c19f255 Merge equal EXPECT NEXT and EXPECT CURRENT in javaBackingFieldUsedInKotlin
• d3df886 Add test for getting default annotation values in KMP
• 3bcac20 Mark testJavaBackingFieldUsedInKotlin as fixed
• e74bb5f Update expected test output in libOrigins
• c9b1d40 Use KSSyntheticJavaBackingFieldImpl in KSPropertyDeclarationImpl
• afefe15 Add KSSyntheticJavaBackingFieldImpl
• 2da07c1 Add test for missing synthetic Java fields
• 7033530 Fix visibility modifiers for Kotlin-based backing fields
• Additional commits viewable in compare view

Updates org.jetbrains.kotlin.plugin.compose from 2.4.10 to 2.4.21

Updates org.jetbrains.kotlin.plugin.serialization from 2.4.10 to 2.4.21

Updates org.jetbrains.kotlin.plugin.serialization from 2.4.10 to 2.4.21

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will 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 version will 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