chore(deps): bump qltysh/qlty-action/install from 141b881236146435192435eb7b0e06ea0b70b4d9 to e50971cef28b66fc1bc8f1d05ccb91c0505aa3d0

[dependabot]

Bumps qltysh/qlty-action/install from 141b881236146435192435eb7b0e06ea0b70b4d9 to e50971cef28b66fc1bc8f1d05ccb91c0505aa3d0.

Changelog

Sourced from qltysh/qlty-action/install'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

• 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
• 2ae1ab3 Update changelog for 2.2.1 release
• 2898852 chore: bump action runtime to node24 (#177)
• 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 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)

[dependabot]

Labels

The following labels could not be found: skip news. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 0%. Comparing base (735e5f5) to head (ceb52b3).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@     Coverage Diff     @@
##   main   #433   +/-   ##
===========================
===========================

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.