Bump qltysh/qlty-action from 2 to 2.2.1 in the github-actions group

[dependabot]

Bumps the github-actions group with 1 update: qltysh/qlty-action.

Updates qltysh/qlty-action from 2 to 2.2.1

Release notes

Sourced from qltysh/qlty-action's releases.

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

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.

... (truncated)

Commits

• b978e80 Update Changelog (#144)
• 8dd860b chore: add smoke tests (#134)
• 54ea76c chore: new release workflow (#130)
• 782ebe0 chore: Release 2.1.0 (#133)
• 57eedc2 fix: Ignore "validate" option when command is "complete" (#132)
• c450c8b Update docs to point to latest version (v2) of coverage action (#131)
• 9e8e09d Change default: validate by default now (#128)
• aa71fdc chore: Update changelog for 1.2.0 (#127)
• a75bce4 chore: Send --no-validate argument to CLI when validate is false (#126)
• cac0a0e fix: Override commit sha for PRs for 'complete' action (#125)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like qltysh/qlty-action is no longer updatable, so this is no longer needed.