Skip to content

Bump qltysh/qlty-action/coverage from 2.0.0 to 2.2.2#11

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/qltysh/qlty-action/coverage-2.2.2
Open

Bump qltysh/qlty-action/coverage from 2.0.0 to 2.2.2#11
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/qltysh/qlty-action/coverage-2.2.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 7, 2026

Copy link
Copy Markdown

Bumps qltysh/qlty-action/coverage from 2.0.0 to 2.2.2.

Release notes

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

v2.2.2

Fixed

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

v2.2.1

  • Bump action runtime to node24

v2.2.0

  • Testing release process (no changes)

v2.1.0

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)

Full Changelog: qltysh/qlty-action@v2.0.0...v2.1.0

Changelog

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

Changelog

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).

We believe this change will significantly improve the accuracy and usability of your coverage data within Qlty. If you have any questions or require assistance, please don't hesitate to contact our support team.

v1.2.0 (2025-08-04)

Fixed

  • Ensure correct commit sha provided from PRs for 'complete' action (#125)
  • More robust error output in face of unknown errors (#121)
  • Set output directory to RUNNER_TEMP (#110)

... (truncated)

Commits
  • 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)
  • dd4b531 Consolidate dev tooling into root devDependencies (#188)
  • 494944c proto: unify npm workspace (single root lockfile, one CI install) (#179)
  • e50971c Fix Dependabot alerts: vitest, vite, rollup, postcss, @​babel/core, picomatch,...
  • fd52dc8 Release v2.2.1 - Update fmt package.json
  • 59f98da Release v2.2.1 - Update coverage package.json
  • Additional commits viewable in compare view

Dependabot compatibility score

You can trigger a rebase of this PR 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 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)

Link to PR: #11

Bumps [qltysh/qlty-action/coverage](https://github.com/qltysh/qlty-action) from 2.0.0 to 2.2.2.
- [Release notes](https://github.com/qltysh/qlty-action/releases)
- [Changelog](https://github.com/qltysh/qlty-action/blob/main/CHANGELOG.md)
- [Commits](qltysh/qlty-action@9e8e09d...b413a89)

---
updated-dependencies:
- dependency-name: qltysh/qlty-action/coverage
  dependency-version: 2.2.2
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Jul 7, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants