Skip to content

test: check stability block position in API markdown#58590

Open
Renegade334 wants to merge 1 commit intonodejs:mainfrom
Renegade334:test-stability-block-position
Open

test: check stability block position in API markdown#58590
Renegade334 wants to merge 1 commit intonodejs:mainfrom
Renegade334:test-stability-block-position

Conversation

@Renegade334
Copy link
Member

The doc generator will only add a stability marker to the index if the blockquote element appears close to the relevant heading. There is an ordering convention (<heading> [<yaml>] <stability>) which is not currently enforced.

Adding a test for this identifies one element which is currently non-compliant, buf.slice() in buffer.md, which does not appear as deprecated in the index due to the malpositioned deprecation block.

@nodejs-github-bot nodejs-github-bot added the needs-ci PRs that need a full CI run. label Jun 5, 2025
@Renegade334 Renegade334 force-pushed the test-stability-block-position branch 2 times, most recently from 7bdc418 to c41bd3e Compare June 5, 2025 19:14
@codecov
Copy link

codecov bot commented Jun 5, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.20%. Comparing base (641653b) to head (91a8078).
⚠️ Report is 1733 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #58590      +/-   ##
==========================================
- Coverage   90.21%   90.20%   -0.01%     
==========================================
  Files         635      635              
  Lines      187494   187495       +1     
  Branches    36838    36818      -20     
==========================================
- Hits       169144   169129      -15     
+ Misses      11145    11117      -28     
- Partials     7205     7249      +44     

see 49 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@Renegade334 Renegade334 force-pushed the test-stability-block-position branch from c41bd3e to 91a8078 Compare June 6, 2025 12:43
@Renegade334 Renegade334 added request-ci Add this label to start a Jenkins CI on a PR. author ready PRs that have at least one approval, no pending requests for changes, and a CI started. labels Nov 15, 2025
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Nov 15, 2025
@nodejs-github-bot

This comment was marked as outdated.

@Renegade334 Renegade334 added request-ci Add this label to start a Jenkins CI on a PR. test Issues and PRs related to the tests. labels Feb 10, 2026
@github-actions github-actions bot removed the request-ci Add this label to start a Jenkins CI on a PR. label Feb 10, 2026
@nodejs-github-bot

This comment was marked as outdated.

@nodejs-github-bot
Copy link
Collaborator

@Renegade334 Renegade334 force-pushed the test-stability-block-position branch from 91a8078 to f523724 Compare February 14, 2026 21:48
@Renegade334
Copy link
Member Author

Rebased as an additional failure case was introduced since the original commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

author ready PRs that have at least one approval, no pending requests for changes, and a CI started. needs-ci PRs that need a full CI run. test Issues and PRs related to the tests.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants