Release v3.0.1

- Improved PR comment formatting with clickable file links
- Added validation for invalid report format configuration
- Added error handling for malformed YAML config files
- Added error handling for invalid custom-matchers JSON input
- Skip annotations with empty messages
- Improved error messages and handling in XML report parsing
- Ensure all annotations have a start line for proper GitHub display
- Added test coverage for invalid YAML config parsing
- Excluded untestable xpath fallback code from coverage reporting

Author: villelahdenvuo

.prettierignore

@@ -3,3 +3,4 @@
 dist/
 node_modules/
 coverage/
+fixtures/invalid-config.yml

CHANGELOG.md

@@ -2,6 +2,20 @@
 
 # Changelog
 
+## [3.0.1] - 2025-12-30
+
+### Fixed
+
+- Improved PR comment formatting with clickable file links when annotations are skipped
+- Added validation for invalid report format configuration
+- Added error handling for malformed YAML config files
+- Added error handling for invalid custom-matchers JSON input
+- Skip annotations with empty messages to avoid creating blank annotations
+- Improved error messages and handling in XML report parsing
+- Ensure all annotations have a start line for proper GitHub display
+- Added test coverage for invalid YAML config parsing error handling
+- Excluded untestable xpath fallback code from coverage reporting
+
 ## [3.0.0] - 2025-12-17
 
 ### Breaking Changes

README.md

@@ -57,31 +57,12 @@ steps:
 
 When the maximum number of annotations per type is reached, additional
 annotations are not displayed as GitHub annotations to avoid clutter. Instead,
-they are added as a comment on the pull request using GitHub's markdown box
-syntax:
-
-- **Error** boxes for skipped error annotations
-- **Warning** boxes for skipped warning annotations
-- **Note** boxes for skipped notice annotations
-
-This ensures that all issues are still visible to developers without
-overwhelming the GitHub UI.
+they are added as a comment on the pull request.
 
 > [!NOTE] For more information about GitHub Actions annotation limitations, see
 > the
 > [official documentation](https://github.com/actions/toolkit/blob/main/docs/problem-matchers.md#limitations).
 
-> [!NOTE]
->
-> You'll need to have a reasonably modern version of
-> [Node.js](https://nodejs.org) handy (20.x or later should work!). If you are
-> using a version manager like [`nodenv`](https://github.com/nodenv/nodenv) or
-> [`fnm`](https://github.com/Schniz/fnm), this template has a `.node-version`
-> file at the root of the repository that can be used to automatically switch to
-> the correct version when you `cd` into the repository. Additionally, this
-> `.node-version` file is used by GitHub Actions in any `actions/setup-node`
-> actions.
-
 ## Custom Matchers
 
 You can define custom matchers to parse your reports and create annotations.

__tests__/main.test.ts

@@ -355,6 +355,9 @@ at Tests.Registration.main(Registration.java:202)`,
 	it('should handle reports with no items', async () => {
 		testInputs.reports = ['junit|fixtures/empty-report.xml'];
 		await main.run();
+		expect(warningMock).toHaveBeenCalledWith(
+			"No items found in fixtures/empty-report.xml using XPath '//testcase'",
+		);
 		expect(errorMock).not.toHaveBeenCalled();
 		expect(setOutputMock).toHaveBeenCalledWith('errors', 0);
 		expect(setOutputMock).toHaveBeenCalledWith('warnings', 0);
@@ -432,4 +435,53 @@ at Tests.Registration.main(Registration.java:202)`,
 			`Failed to create PR comment: ${apiError}`,
 		);
 	});
+
+	it('should throw error for invalid report format', async () => {
+		testInputs.reports = ['invalid-format-no-pipe'];
+		await expect(main.run()).rejects.toThrow(
+			"Invalid report format: 'invalid-format-no-pipe'. Expected 'matcher|patterns'.",
+		);
+	});
+
+	it('should handle missing config file', async () => {
+		testInputs.configPath = '/nonexistent/config.yml';
+		await main.run();
+		expect(infoMock).toHaveBeenCalledWith(
+			'No config file found at /nonexistent/config.yml.',
+		);
+	});
+
+	it('should throw error for invalid custom-matchers JSON', async () => {
+		testInputs['custom-matchers'] = '{invalid json';
+		await expect(main.run()).rejects.toThrow();
+		expect(errorMock).toHaveBeenCalledWith(
+			expect.stringContaining('Failed to parse custom-matchers input'),
+		);
+	});
+
+	it('should throw error for invalid YAML config', async () => {
+		testInputs.configPath = 'fixtures/invalid-config.yml';
+		await expect(main.run()).rejects.toThrow();
+		expect(errorMock).toHaveBeenCalledWith(
+			expect.stringContaining(
+				'Failed to parse YAML config at fixtures/invalid-config.yml',
+			),
+		);
+	});
+
+	it('should skip items with empty messages', async () => {
+		testInputs['custom-matchers'] = `{
+			"custom-matcher": {
+				"format": "xml",
+				"item": "//testCase",
+				"message": "@empty",
+				"file": "@file",
+				"startLine": "@line"
+			}
+		}`;
+		testInputs.reports = ['custom-matcher|fixtures/custom-format.xml'];
+		await main.run();
+		// Should not create any annotations since message is empty
+		expect(setOutputMock).toHaveBeenCalledWith('total', 0);
+	});
 });

dist/index.js

@@ -0,0 +1,7 @@
+reports:
+  - junit|fixtures/junit-generic.xml
+maxAnnotations: 10
+invalid: yaml: content:
+  - with
+    bad: indentation
+    [unclosed bracket

dist/index.js.map

@@ -1,7 +1,7 @@
 {
 	"name": "report-annotate",
 	"description": "Annotate PR from report e.g. junit",
-	"version": "3.0.0",
+	"version": "3.0.1",
 	"author": "",
 	"type": "module",
 	"private": true,