Skip to content

Commit 782ebe0

Browse files
noahd1Copilot
andauthored
chore: Release 2.1.0 (#133)
* Update Changelog for missed 2.0.0 entry * Prepare release 2.1.0 * Update CHANGELOG.md Co-authored-by: Copilot <[email protected]> --------- Co-authored-by: Copilot <[email protected]>
1 parent 57eedc2 commit 782ebe0

File tree

3 files changed

+28
-2
lines changed

3 files changed

+28
-2
lines changed

CHANGELOG.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,31 @@
11
# Changelog
22

3+
## v2.1.0 (2025-08-08)
4+
5+
### New
6+
7+
- support "dry-run" option for command `complete`
8+
9+
### Improved
10+
11+
- Use log level "error" instead of "warning" when a catastrophic error occurs but "skip-errors" is true
12+
13+
### Fixed
14+
15+
- Ignore "validate" option when command is "complete" (otherwise errors with invalid option)
16+
17+
## v2.0.0 (2025-08-05)
18+
19+
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.
20+
21+
What This Means for You:
22+
23+
- 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)
24+
- 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.
25+
- 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).
26+
27+
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.
28+
329
## v1.2.0 (2025-08-04)
430

531
### Fixed

coverage/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"name": "qlty-action-coverage",
33
"description": "Reusable GitHub Action to upload code coverage to Qlty Cloud",
4-
"version": "1.0.0",
4+
"version": "2.1.0",
55
"author": "Qlty Software Inc.",
66
"homepage": "https://github.com/qltysh/qlty-action/tree/main/coverage",
77
"repository": {

fmt/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
{
22
"name": "qlty-action-fmt",
33
"description": "Resuable GitHub Action to auto-format code with Qlty CLI",
4-
"version": "0.0.0",
4+
"version": "2.1.0",
55
"author": "Qlty Software Inc.",
66
"homepage": "https://github.com/qltysh/qlty-action/tree/main/fmt",
77
"repository": {

0 commit comments

Comments
 (0)