Bump qltysh/qlty-action/coverage from 2.2.0 to 2.3.0

[dependabot]

Bumps qltysh/qlty-action/coverage from 2.2.0 to 2.3.0.

Release notes

Sourced from qltysh/qlty-action/coverage's releases.

v2.3.0

New

• Add a selected input to the coverage action for marking an upload as covering a selected subset of the test suite, which contributes to diff coverage only and is excluded from total coverage (#200)

v2.2.3

• Internal release process improvements (no user-facing changes) (#196)

v2.2.2

Fixed

• Security updates to bundled dependencies (#190, #191)

v2.2.1

• Bump action runtime to node24

Changelog

Sourced from qltysh/qlty-action/coverage's changelog.

Changelog

v2.3.0 (2026-07-09)

New

• Add a selected input to the coverage action for marking an upload as covering a selected subset of the test suite, which contributes to diff coverage only and is excluded from total coverage (#200)

v2.2.3 (2026-07-07)

• Internal release process improvements (no user-facing changes) (#196)

v2.2.2 (2026-07-07)

Fixed

• Security updates to bundled dependencies (#190, #191)

v2.2.1 (2026-06-02)

• Bump action runtime to node24

v2.2.0 (2025-08-11)

• Testing release process (no changes)

v2.1.0 (2025-08-08)

New

• support "dry-run" option for command complete

Improved

• Use log level "error" instead of "warning" when a catastrophic error occurs but "skip-errors" is true

Fixed

• Ignore "validate" option when command is "complete" (otherwise errors with invalid option)

v2.0.0 (2025-08-05)

This release mirrors the breaking change we introduced in the qlty CLI proper: we now validate coverage data by default instead of uploading coverage data to qlty that qlty cannot use. Now you must opt out of this behavior whereas previously opt in.

What This Means for You:

• If coverage reporting is working as expected, you'll experience no impact. If you're uploading valid reports and seeing directory and file-level coverage metrics in Qlty, you don't need to do anything. (If your reports include mismatched paths, you'll see specific path errors listed within your CI output)
• Potential CI Build Failures: Once this change is implemented, if your current CI/CD pipeline uploads a report with mismatched paths, your builds will begin to fail when executing qlty coverage publish.
• Quick Fix for Build Failures: If your builds start failing and you need to get them passing immediately, you can temporarily add validate: false to the GitHub Action configuration. This will disable validation and allow your CI build to pass (though your coverage data will remain broken until you've uploaded a valid report).

... (truncated)

Commits

• 08a0a86 Prepare release v2.3.0 (#201)
• 8b0d5e5 Add selected input to the coverage action (#200)
• dafbc1e Prepare release v2.2.3 (#197)
• bb4c677 Announce releases to #feed-deploys (#196)
• c9fe6ae Group security dependency fixes into one changelog item (#195)
• b413a89 Release v2.2.2 (#194)
• bbb11a9 Automate changelog drafting in the release process (#193)
• 3baf1fc Fix Dependabot alerts in .qlty/configs: js-yaml, ajv, @​eslint/plugin-kit (#192)
• 9341197 Fix @​opentelemetry/core Dependabot alerts: @​sentry/node 9 -> 10 (#191)
• 1d3373b Fix undici Dependabot alerts via root override to ^6.27.0 (#190)
• Additional commits viewable in compare view

[qltysh]

Coverage Impact

This PR will not change total coverage.

🚦 See full report on Qlty Cloud »

🛟 Help

• Diff Coverage: Coverage for added or modified lines of code (excludes deleted files). Learn more.

• Total Coverage: Coverage for the whole repository, calculated as the sum of all File Coverage. Learn more.

• File Coverage: Covered Lines divided by Covered Lines plus Missed Lines. (Excludes non-executable lines including blank lines and comments.)

  • Indirect Changes: Changes to File Coverage for files that were not modified in this PR. Learn more.

[jreineckearm]

@dependabot rebase

[jreineckearm]

@dependabot recreate