chore(deps): update dependency org.jetbrains.dokka to v2

[renovate-self-hosted-apter]

This PR contains the following updates:

Package	Type	Update	Change
org.jetbrains.dokka	plugin	major	1.9.20 -> 2.0.0

---

Release Notes

Kotlin/dokka (org.jetbrains.dokka)

v2.0.0: 2.0.0

Dokka 2.0.0 focuses on simplifying configuration and preparing for support of future Kotlin language features. Key highlights include:

• Dokka Gradle Plugin v2: revamped Gradle plugin based on Dokkatoo.
• Experimental K2 Analysis: support for K2 compiler frontend.
• HTML Improvements: better accessibility and easier customization.

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

Dokka's Gradle plugin v2 based on Dokkatoo

Please check the migration guide for the update procedure and give feedback!

Dokka 2.0.0 introduces significant improvements to Dokka Gradle plugin, aligning more closely with Gradle best practices:

• Adopts Gradle types, which leads to better performance.
• Uses an intuitive top-level DSL configuration instead of a low-level task-based setup, which simplifies the build scripts and their readability.
• Takes a more declarative approach to documentation aggregation, which makes multi-project documentation easier to manage.
• Uses a type-safe plugin configuration, which improves the reliability and maintainability of your build scripts.
• Fully supports Gradle configuration cache and build cache, which improves performance and simplifies build work.

Changes from Dokka 2.0.0-Beta

• Forward Dokka Generator messages to Gradle logger (https://github.com/Kotlin/dokka/pull/3833)
• Add deprecated property to help migrate from JSON Dokka plugin configuration (https://github.com/Kotlin/dokka/pull/3877)
• Rename dokkaPublicationDirectory to basePublicationsDirectory (https://github.com/Kotlin/dokka/pull/3876)
• Rename dokkaModuleDirectory, and mark as internal (https://github.com/Kotlin/dokka/pull/3880)
• Update and add KDoc for DGPv2 (https://github.com/Kotlin/dokka/pull/3842)
• Remove DokkaPluginParametersBuilder (https://github.com/Kotlin/dokka/pull/3872)
• Increase default max heap of Worker to 2G (https://github.com/Kotlin/dokka/pull/3913)
• Remove the dependency of dokkaGenerate on dokkaGenerateModule* (https://github.com/Kotlin/dokka/pull/3920)
• KT-71784 Fix classpath for KMP shared source sets (https://github.com/Kotlin/dokka/pull/3942)
• Fix DGP/KMP integration, so Dokka can 'see' code from shared source sets in target source sets (https://github.com/Kotlin/dokka/pull/3814)

Dokka's K2 analysis

Dokka 2.0.0 introduces K2 analysis, which is currently in an experimental stage. 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. We are actively working towards stabilizing K2 analysis and are planning to enable K2 analysis by default in future.

To opt in to Dokka's K2 analysis, add the following flag to your project's gradle.properties file:

org.jetbrains.dokka.experimental.tryK2=true

Known limitations:

• Intersecting source roots (#​3701) and intersecting sample roots (#​3373) may cause issues.
• Kotlin/JS libraries compiled with the legacy Kotlin/JS compiler are not supported (#​3751).

We would greatly value your feedback if you encounter any of these limitations.

Potential differences between the outputs of K1 and K2:

While the output of K2 analysis aims to align with K1, there are some differences to be aware of:

• Java synthetic properties: rendering may vary (details).
• KDoc links: resolution and rendering differences (details).
• Inconsistent documentable rendering order (#​3590).
• Enum entries: anonymous and overridden methods are no longer rendered (#​3129).
• Other differences may arise due to variations in type inference between K1 and K2.

HTML format

Dokka 2.0.0 introduces some changes to HTML output. We updated the structure of some elements and classes, particularly in the navigation and sidebar, to improve accessibility and simplify maintenance. These changes only affect you if you previously customized Dokka styles.

• We removed redundant wrappers like navigation--inner and navigation-title.
• We reworked blocks such as versions-dropdown to make them more accessible.
• We renamed classes like navigation-controls--homepage to improve consistency. For example, it’s now called navigation-controls--btn_homepage.

For more information, see the pull request.

The easiest way to update your current templates is to adjust the new templates to your needs.

Bugfixes

• Fix merging expect-actual declarations (https://github.com/Kotlin/dokka/pull/3875)

Other changes

• Update the external link URL for stdlib (https://github.com/Kotlin/dokka/pull/3938)

Feedback

We would appreciate your feedback!

• Please report any feedback or problems https://kotl.in/dokka-issues
• Chat with the community visit #dokka in https://kotlinlang.slack.com/ (To sign up visit https://kotl.in/slack)

Full Changelog: Kotlin/dokka@v1.9.20...v2.0.0

---

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Branch Coverage (ubuntu-24.04)

Total Project Coverage	69.91%	✅

[github-actions]

Line Coverage (ubuntu-24.04)

Total Project Coverage	92.01%	✅

[github-actions]

Branch Coverage (windows-2022)

Total Project Coverage	69.91%	✅

[github-actions]

Line Coverage (windows-2022)

Total Project Coverage	92.01%	✅