Repository navigation
Release 0.1.1 - #18
Conversation
|
No actionable comments were generated in the recent review.
 |
| Layer / File(s) | Summary |
|---|---|
Update package version package.json |
The package version changes from 0.1.0 to 0.1.1. |
Estimated code review effort: 1 (Trivial) | ~2 minutes
Change: Other
Possibly related PRs
- Project516/java-web#99: This PR checks that the release tag version matches the version in
package.json.
Suggested reviewers: project516-review-bot
Merge Risk: 
08b5c
-
The version-only change is ready to merge.
Pre-merge checks: 
-
Check name Status Explanation Title check The title clearly identifies the release version and matches the package version change from 0.1.0 to 0.1.1. Description check The description explains the version bump and lists changes included since version 0.1.0. It is related to the changeset. Docstring Coverage No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentat… Linked Issues check Check skipped because no linked issues were found for this pull request. Out of Scope Changes check Check skipped because no linked issues were found for this pull request. Full details: Docstring Coverage
-
Explanation
No eligible functions found in the changed files. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff with cyclomatic complexity of at least 2. Documentation-only edits and deletions within surviving functions are included; unchanged diff context and fully deleted functions are excluded. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)
-
Finishing Touches
-
Simplify code
-
- Commit to this branch
- Create a new PR
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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.
A rabbit checks the version line
From zero one to zero one one
The package wears a newer sign
The carrot patch has just begun
Then hops away beneath the sun
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
![project516-review-bot[bot]](https://avatars.githubusercontent.com/in/4903871?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR bumps the version from 0.1.0 to 0.1.1 in package.json. The change is a single line version increment appropriate for a patch release containing the bug fixes and improvements listed in the description.
review-bot, model nvidia/nemotron-3-ultra-550b-a55b:free, verdict approve
Bumps the version to 0.1.1. Once this merges, publishing the GitHub release
v0.1.1from master runs the release workflow, which runs every OpenJDK test and publishes to npm.Since 0.1.0:
java-webcommand honors-Xmxas x64 HotSpot does: it caps one allocation and sets whatRuntime.maxMemory()and the memory MXBean report, rounds up to 2 MB steps, and refuses sizes under 2 MB or malformed values (Honor -Xmx under the java-web command #13).java-web Main | head -1) no longer crashes the command: writes fail withIOException: Broken pipeandSystem.out.checkError()turns true, as on HotSpot (Handle a closed stdout like HotSpot #10).javaWebWriteStdinis documented, and calling it beforecheerpjInitthrows a clear error (Document javaWebWriteStdin #11).masterrequires them (Run the OpenJDK tests in CI, split and picked by change #12, Keep a green pull request green on master and at release #14);@types/node26.6.6 and Node 26 in CI (Update dependency @types/node to v26.6.6 #16, Update dependency node to v26 #17).