search

ForNeVeR / Todosaurus

IntelliJ Plaform plugin to manage TODO comments in the code.
https://plugins.jetbrains.com/plugin/23838
Other
12 stars 2 forks source link

Bump org.jetbrains.kotlinx.kover from 0.7.5 to 0.7.6 #8

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 8 months ago

Bumps org.jetbrains.kotlinx.kover from 0.7.5 to 0.7.6.

Release notes

Sourced from org.jetbrains.kotlinx.kover's releases.

0.7.6

Kover Gradle Plugin

Features

  • 527 Added the ability to specify a header for an XML report

Bugfixes

  • 510 Fixed Stream closed error when generating Kover HTML report
  • 513 Fixed breaking configuration cache
  • 517 Fixed incorrect marking of first function line when parameters with default value are used
  • 530 Fixed the presence of classes instrumented with Robolectric in Jacoco reports
  • 543 Fixed package exclusion in reports for JaCoCo

Kover Offline

Features

  • 534 Created Kover features artifact to invoke the capabilities of Kover programmatically
Changelog

Sourced from org.jetbrains.kotlinx.kover's changelog.

0.7.6 / 2024-02-16

Kover Gradle Plugin

Features

  • 527 Added the ability to specify a header for an XML report

Bugfixes

  • 510 Fixed Stream closed error when generating Kover HTML report
  • 513 Fixed breaking configuration cache
  • 517 Fixed incorrect marking of first function line when parameters with default value are used
  • 530 Fixed the presence of classes instrumented with Robolectric in Jacoco reports
  • 543 Fixed package exclusion in reports for JaCoCo

Kover Offline

Features

  • 534 Created Kover features artifact to invoke the capabilities of Kover programmatically
Commits
  • 0575a68 Automated publication of documentation
  • e80c83c Release 0.7.6
  • 896699e Fixed package exclusion in reports for JaCoCo
  • 5380bc9 Implemented Kover Features artifact to integration with Android Gradle Plugin
  • ec84816 Added the ability to specify a header for an XML report
  • 1d6f64a Fixed Stream closed error when generating Kover HTML report
  • f0d57ca Fixed the presence of classes instrumented with Robolectric in Jacoco reports
  • 56f8fd5 Fix breaking configuration cache
  • e8ffbda Update Gradle Dokka configuration to make sure "source" button is visible in ...
  • See full diff in compare view


Dependabot compatibility score

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 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)
github-actions[bot] commented 8 months ago

Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

View the detailed Qodana report To be able to view the detailed Qodana report, you can either: 1. Register at [Qodana Cloud](https://qodana.cloud/) and [configure the action](https://github.com/jetbrains/qodana-action#qodana-cloud) 2. Use [GitHub Code Scanning with Qodana](https://github.com/jetbrains/qodana-action#github-code-scanning) 3. Host [Qodana report at GitHub Pages](https://github.com/JetBrains/qodana-action/blob/3a8e25f5caad8d8b01c1435f1ef7b19fe8b039a0/README.md#github-pages) 4. Inspect and use `qodana.sarif.json` (see [the Qodana SARIF format](https://www.jetbrains.com/help/qodana/qodana-sarif-output.html#Report+structure) for details) To get `*.log` files or any other Qodana artifacts, run the action with `upload-result` option set to `true`, so that the action will upload the files as the job artifacts: ```yaml - name: 'Qodana Scan' uses: JetBrains/qodana-action@v2023.3.1 with: upload-result: true ```
Contact Qodana team Contact us at [qodana-support@jetbrains.com](mailto:qodana-support@jetbrains.com) - Or via our issue tracker: https://jb.gg/qodana-issue - Or share your feedback: https://jb.gg/qodana-discussions