Skip to content

Conversation

@RobinTail
Copy link
Owner

@RobinTail RobinTail commented Aug 31, 2025

Summary by CodeRabbit

  • Documentation

    • Added changelog entry for v2.0.0 documenting supported Node.js versions: ^20.19.0 || ^22.12.0 || ^24.0.0.
  • Chores

    • Declared supported Node.js versions in package metadata to improve install-time compatibility checks; users on unsupported Node versions may see warnings or install blocks.
    • Bumped package version to 2.0.0-beta.2; no functional or API changes.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Aug 31, 2025

Walkthrough

Added a v2.0.0 changelog entry and updated zod-plugin/package.json to bump the package version to 2.0.0-beta.2 and restrict supported Node.js engines to ^20.19.0 || ^22.12.0 || ^24.0.0. No exported/public API declarations changed.

Changes

Cohort / File(s) Summary
Changelog update
zod-plugin/CHANGELOG.md
Added "Version 2" / v2.0.0 entry documenting restricted supported Node.js versions.
Package metadata update
zod-plugin/package.json
Bumped version to 2.0.0-beta.2 and added `engines.node: "^20.19.0

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • Detaching Zod plugin #2869 — Modifies zod-plugin/package.json/packaging metadata and is closely related to version/metadata changes.

Suggested labels

documentation

Poem

I hop through changelogs with a curious nose,
Version flags flutter where the carrot-path goes.
Engines set snug, the burrow's tree aligned,
A tiny release, gentle as a bind. 🐇

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title clearly and concisely summarizes the primary change of adding Node engine restrictions to the zod-plugin. It accurately reflects the modifications in package.json and the PR objectives without extraneous detail or noise. The scope and action are immediately clear to reviewers and maintainers.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch ensure-engines-plugin

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 361c85c and 9caaefb.

📒 Files selected for processing (1)
  • zod-plugin/package.json (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • zod-plugin/package.json

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 and usage tips.

@coveralls-official
Copy link

coveralls-official bot commented Aug 31, 2025

Coverage Status

coverage: 100.0%. remained the same
when pulling 40cfb8c on ensure-engines-plugin
into 50116f2 on master.

@RobinTail RobinTail marked this pull request as ready for review September 21, 2025 06:44
@RobinTail
Copy link
Owner Author

My concern here is that technically it is a breaking change.

@RobinTail RobinTail added the breaking Backward incompatible changes label Sep 23, 2025
@RobinTail
Copy link
Owner Author

✅ checked the published code

@RobinTail RobinTail merged commit c0414ab into master Sep 27, 2025
5 checks passed
@RobinTail RobinTail deleted the ensure-engines-plugin branch September 27, 2025 05:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking Backward incompatible changes prevention

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants