build(deps): bump dokka from 2.0.0 to 2.1.0

[dependabot[bot]]

Bumps dokka from 2.0.0 to 2.1.0. Updates org.jetbrains.dokka:dokka-gradle-plugin from 2.0.0 to 2.1.0

Release notes

Sourced from org.jetbrains.dokka:dokka-gradle-plugin's releases.

2.1.0

Dokka 2.1.0 focuses on stabilizing experimental features, supporting new Kotlin language features, and improving the user experience. Key highlights include:

• Dokka Gradle Plugin v2 is enabled by default!
• K2 Analysis is enabled by default!
• Support for Context parameters and Nested typealiases
• HTML format refinement: better accessibility and consistency across all components
• Multiple performance and compatibility improvements

More details about each of the changes below. See Dokka 2.1.0 milestone for the list of all changes.

Dokka's Gradle plugin v2 is enabled by default!

Please check the migration guide for the update procedure

Dokka 2.0.0 introduced a significantly improved Gradle plugin v2, and with Dokka 2.1.0 it is now enabled by default! As a result, all types and Gradle tasks related to Dokka Gradle plugin v1 are deprecated and will be removed in future releases. Running Gradle tasks related to Dokka Gradle plugin v1 will result in an error during execution.

Starting from this release, the minimum supported Gradle version is 7.6.3.

Other fixes and improvements

• Update Gradle Properties types to be non-nullable (Kotlin/dokka#4136)
• Update displayName convention for DokkaSourceSets (Kotlin/dokka#4142)
• Update olderVersionsDir to be an optional input. (Kotlin/dokka#4155)
• Add lifecycle tasks for generating formats (Kotlin/dokka#4141)
• Use project name as default modulePath for root project to avoid clashing outputs during aggregation (Kotlin/dokka#4158)
• Remove Dokka debug config file from task outputs (Kotlin/dokka#3961)
• Remove V2EnabledWithHelpers warning & info message (Kotlin/dokka#4206)

Dokka's K2 analysis is enabled by default!

Dokka 2.1.0fixes the most problematic issues with K2 analysis and makes it enabled by default! In addition to this, Dokka 2.1.0with K2 analysis introduces support for context parameters and nested typealiases!

Dokka's K2 analysis leverages Kotlin's K2 compiler frontend for analysing code and uses the same shared Analysis API, which is used in IntelliJ IDEA’s K2 mode. The output with K2 analysis should mostly match that of K1 analysis, but there may be minor differences.

If you previously opted in to Dokka's K2 analysis, remove org.jetbrains.dokka.experimental.tryK2 from your project's gradle.properties file. Dokka's K1 analysis is still available, but it is deprecated and will be removed in future releases. We would greatly appreciate your feedback, if there is something that is blocking you from migrating to K2 analysis!

Other fixes and improvements

• Fix merging of implicit expect/actual with a single declaration (Kotlin/dokka#4016)
• Support Wasm platform fully (Kotlin/dokka#4123)
• Fix override modifier for generic functions (Kotlin/dokka#4126)
• Add a receiver to accessor DRI (Kotlin/dokka#4122)
• Fix param tag for type parameter on implicit primary constructor (Kotlin/dokka#4154)

... (truncated)

Commits

• 905286d Update Dokka version references to 2.1.0 (#4297)
• a3376d1 Update the version for the 2.1.0 release
• cbba0c9 fix: spacing in html output (#4292)
• 16eac59 Support for nested typealiases (#4261)
• 454c687 Handle InvocationTargetException exception explicitly in DokkaBootstrap (...
• 7626540 Follow symbolic links when building KaModule for AA standalone session (#4264)
• e4c7474 Build the Dokka Maven Plugin with the lastest compiler version (#4228)
• 7a63b38 Update the version for the 2.1.0-Beta release
• bbde1ac Update AA to 2.3.0-dev-4019 (#4219)
• fa41f6d Set the 2.1.0-SNAPSHOT version for consistency (#4225)
• Additional commits viewable in compare view

Updates org.jetbrains.dokka:dokka-base from 2.0.0 to 2.1.0

Release notes

Sourced from org.jetbrains.dokka:dokka-base's releases.

2.1.0

Dokka 2.1.0 focuses on stabilizing experimental features, supporting new Kotlin language features, and improving the user experience. Key highlights include:

• Dokka Gradle Plugin v2 is enabled by default!
• K2 Analysis is enabled by default!
• Support for Context parameters and Nested typealiases
• HTML format refinement: better accessibility and consistency across all components
• Multiple performance and compatibility improvements

More details about each of the changes below. See Dokka 2.1.0 milestone for the list of all changes.

Dokka's Gradle plugin v2 is enabled by default!

Please check the migration guide for the update procedure

Dokka 2.0.0 introduced a significantly improved Gradle plugin v2, and with Dokka 2.1.0 it is now enabled by default! As a result, all types and Gradle tasks related to Dokka Gradle plugin v1 are deprecated and will be removed in future releases. Running Gradle tasks related to Dokka Gradle plugin v1 will result in an error during execution.

Starting from this release, the minimum supported Gradle version is 7.6.3.

Other fixes and improvements

• Update Gradle Properties types to be non-nullable (Kotlin/dokka#4136)
• Update displayName convention for DokkaSourceSets (Kotlin/dokka#4142)
• Update olderVersionsDir to be an optional input. (Kotlin/dokka#4155)
• Add lifecycle tasks for generating formats (Kotlin/dokka#4141)
• Use project name as default modulePath for root project to avoid clashing outputs during aggregation (Kotlin/dokka#4158)
• Remove Dokka debug config file from task outputs (Kotlin/dokka#3961)
• Remove V2EnabledWithHelpers warning & info message (Kotlin/dokka#4206)

Dokka's K2 analysis is enabled by default!

Dokka 2.1.0fixes the most problematic issues with K2 analysis and makes it enabled by default! In addition to this, Dokka 2.1.0with K2 analysis introduces support for context parameters and nested typealiases!

Dokka's K2 analysis leverages Kotlin's K2 compiler frontend for analysing code and uses the same shared Analysis API, which is used in IntelliJ IDEA’s K2 mode. The output with K2 analysis should mostly match that of K1 analysis, but there may be minor differences.

If you previously opted in to Dokka's K2 analysis, remove org.jetbrains.dokka.experimental.tryK2 from your project's gradle.properties file. Dokka's K1 analysis is still available, but it is deprecated and will be removed in future releases. We would greatly appreciate your feedback, if there is something that is blocking you from migrating to K2 analysis!

Other fixes and improvements

• Fix merging of implicit expect/actual with a single declaration (Kotlin/dokka#4016)
• Support Wasm platform fully (Kotlin/dokka#4123)
• Fix override modifier for generic functions (Kotlin/dokka#4126)
• Add a receiver to accessor DRI (Kotlin/dokka#4122)
• Fix param tag for type parameter on implicit primary constructor (Kotlin/dokka#4154)

... (truncated)

Commits

• 905286d Update Dokka version references to 2.1.0 (#4297)
• a3376d1 Update the version for the 2.1.0 release
• cbba0c9 fix: spacing in html output (#4292)
• 16eac59 Support for nested typealiases (#4261)
• 454c687 Handle InvocationTargetException exception explicitly in DokkaBootstrap (...
• 7626540 Follow symbolic links when building KaModule for AA standalone session (#4264)
• e4c7474 Build the Dokka Maven Plugin with the lastest compiler version (#4228)
• 7a63b38 Update the version for the 2.1.0-Beta release
• bbde1ac Update AA to 2.3.0-dev-4019 (#4219)
• fa41f6d Set the 2.1.0-SNAPSHOT version for consistency (#4225)
• Additional 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 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)