Bump qltysh/qlty-action from 1 to 2

[dependabot]

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

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

• Make files arg optional for complete (#112)

Commits

• 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)
• See full diff 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 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 <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)

[aivus]

@dependabot recreate