docs: name the row in release notes while 0.x folds the signal

[electrohyun]

Summary

0019 shifts every row one place to the right below 1.0.0, and says so, but does not say what the shift costs. Two rows that differ above 1.0.0 land on the same number below it, so a 0.x patch can be a delivery correction or a comment typo and the digit does not separate them.

This records where the separation lives instead. Every release below 1.0.0 names the row it landed on, which v0.4.1's notes already do.

It matters for the next one rather than for this one. The emit and on return values are an observable change that the shift puts in a patch, so without this sentence 0.4.2 would be the first release the rule quietly fails to describe.

Related issue

No tracking issue. Follow-up to #177, which is already merged, so it lands as its own pull request rather than a commit on that branch.

Checklist

• Tests added or updated. Documentation only.
• Behavior verified against real socket.io. No source change.

[coderabbitai]

Warning

Review limit reached

@electrohyun, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 21 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: d0d6e902-320c-4966-86c4-61520a79be3f

📥 Commits

Reviewing files that changed from the base of the PR and between 8e6e012 and b169165.

📒 Files selected for processing (1)

• docs/decisions/0019-what-counts-as-a-breaking-change.md

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}