Bump qltysh/qlty-action from 1 to 2 in the github-actions group across 1 directory

[dependabot]

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

Updates qltysh/qlty-action from 1 to 2

Release notes

Sourced from qltysh/qlty-action's releases.

v2.0.0

This release mirrors the breaking change we introduced in the qlty CLI proper: we now validate coverage data by default instead of uplpoading 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)

Thank you, @​enell for your contribution!

Full Changelog: qltysh/qlty-action@v1.1.1...v1.2.0

v1.1.1

What's Changed

• Make files arg optional for complete by @​marschattha in qltysh/qlty-action#112

Full Changelog: qltysh/qlty-action@v1.1.0...v1.1.1

v1.1.0

What's Changed

• Update to use newer, simpler prefix args by @​brynary in qltysh/qlty-action#84
• Add format input by @​brynary in qltysh/qlty-action#85
• Add dry-run input parameter by @​brynary in qltysh/qlty-action#88
• Add incomplete flag option to coverage action by @​brynary in qltysh/qlty-action#89
• Add name input option to coverage action by @​brynary in qltysh/qlty-action#90
• Allow dry-run without authentication by @​brynary in qltysh/qlty-action#91
• Add support for installing Qlty on Windows to coverage action by @​brynary in qltysh/qlty-action#87
• Add validate and validate-file-threshold inputs by @​brynary in qltysh/qlty-action#95
• Add command input to coverage action ("publish" the default, or "complete") by @​brynary in qltysh/qlty-action#96
• Change 'files' parameter to only be required when command is publish by @​noahd1 in qltysh/qlty-action#103

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

Changelog

Sourced from qltysh/qlty-action's changelog.

Changelog

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)

Thank you, @​enell for your contribution!

v1.1.1 (2025-06-25)

Improved

... (truncated)

Commits

• fd52dc8 Release v2.2.1 - Update fmt package.json
• 59f98da Release v2.2.1 - Update coverage package.json
• 2ae1ab3 Update changelog for 2.2.1 release
• 2898852 chore: bump action runtime to node24 (#177)
• 141b881 Fix Dependabot alerts: minimatch (#172)
• 7d2645a feat: Add Claude Code hook to auto-package dist/ on source edits (#171)
• 0814173 feat: Add sigstore attestation verification and extract shared installer pack...
• 781c27d Bump node version to 22.22 (#169)
• ea1f343 Upgrade js yaml (#168)
• ea1eaf4 Add "dotcover" and "xccov-json" to list of supported formats (#167)
• Additional commits viewable in compare view

[dependabot]

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