feat: improve changes issues positions

[araujogui]

Description

Improve invalid-change-version to provide users with more precise issue locations instead of only the entire YAML node position.

Validation

npx api-docs-tooling lint -i doc/api/*.md

Related Issues

Check List

• I have read the Contributing Guidelines and made commit messages that follow the guideline.
• I have run node --run test and all tests passed.
• I have check code formatting with node --run format & node --run lint.
• I've covered new added functionality with unit tests if necessary.

[codecov]

Codecov Report

Attention: Patch coverage is 92.85714% with 11 lines in your changes missing coverage. Please review.

Project coverage is 49.70%. Comparing base (276687e) to head (fcb1341).
Report is 5 commits behind head on main.

✅ All tests successful. No failed tests found.

Files with missing lines	Patch %	Lines
src/linter/utils/yaml.mjs	92.20%	6 Missing ⚠️
src/linter/rules/invalid-change-version.mjs	93.33%	5 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #313      +/-   ##
==========================================
+ Coverage   48.90%   49.70%   +0.79%     
==========================================
  Files          82       83       +1     
  Lines        6825     6949     +124     
  Branches      277      295      +18     
==========================================
+ Hits         3338     3454     +116     
- Misses       3484     3492       +8     
  Partials        3        3              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

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

[Copilot]

Pull Request Overview

This PR refactors the invalid-change-version linter rule to leverage the YAML AST for pinpoint issue locations, adds supporting YAML utilities, and updates tests and constants to match the new behavior.

• Introduce YAML AST helpers (findPropertyByName, normalizeNode, createYamlIssueReporter)
• Refactor invalid-change-version to parse with yaml's LineCounter and report precise lines
• Update tests and add a new lint message for invalid change property types

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/utils/parser/index.mjs	Adjusted JSDoc to accept import('mdast').Node instead of Html
src/linter/utils/yaml.mjs	New YAML utilities for property lookup, normalization, and issue reporting
src/linter/rules/invalid-change-version.mjs	Refactored rule to use AST parsing and createYamlIssueReporter
src/linter/rules/tests/invalid-change-version.test.mjs	Updated tests for new error positions and added invalid-property case
src/linter/constants.mjs	Added invalidChangeProperty lint message

Comments suppressed due to low confidence (3)

src/linter/utils/yaml.mjs:40

• [nitpick] Make the error message more descriptive by including the actual node type encountered (e.g., using node.type), rather than hard-coding "map".

throw new Error(`Unexpected node type: map`);

src/linter/utils/yaml.mjs:50

• There are currently no unit tests for createYamlIssueReporter. Consider adding tests that verify correct line calculations based on a mock LineCounter and sample nodes.

export const createYamlIssueReporter = (yamlNode, lineCounter) => {

src/linter/rules/tests/invalid-change-version.test.mjs:72

• [nitpick] The variable name first_call uses snake_case; consider using camelCase (e.g., firstCall) to stay consistent with project style.

const first_call = context.report.mock.calls[0];

[AugustinMauroy]

LGMT ! just try to cover all line with test

[avivkeller]

bump @nodejs/web-infra

[ovflowd]

LGTM

[avivkeller]

I wonder why CI is green 🤔? #318

[AugustinMauroy]

Is the test is correctly run ?