Skip to content

docs(changelog): prepare v0.3.9 release - #93

Merged
xusd320 merged 1 commit into
mainfrom
xusd320/release-v0.3.9
Aug 11, 2026
Merged

docs(changelog): prepare v0.3.9 release#93
xusd320 merged 1 commit into
mainfrom
xusd320/release-v0.3.9

Conversation

@xusd320

@xusd320 xusd320 commented Aug 11, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Prepare the changelog for the next stable 0.3 release, v0.3.9.
  • Capture the single feature merged after v0.3.8.

Changes

  • Leave the Unreleased section empty for future changes.
  • Add a dated v0.3.9 section for the dev server ready plugin hook from feat(plugin): expose dev server ready hook #92.
  • Keep source package versions and internal dependency ranges unchanged; release automation owns publish-time versioning.

Validation

  • npm run lint
  • npm --workspace evjs-docs run build
  • git diff --check

Risk / rollout

  • Low risk: this PR changes only release metadata in CHANGELOG.md.
  • Publishing occurs separately when the v0.3.9 GitHub Release is created after merge.

Reviewer notes

  • Verify the v0.3.9 entry matches the complete v0.3.8...main commit range.

@coderabbitai

coderabbitai Bot commented Aug 11, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 52 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: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c78a6e1d-5d80-4ef1-a1c3-ea75a5997f72

📥 Commits

Reviewing files that changed from the base of the PR and between 2670ad2 and d6cbbdc.

📒 Files selected for processing (1)
  • CHANGELOG.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

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

@xusd320
xusd320 merged commit d1099dd into main Aug 11, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant