Conversation
There was a problem hiding this comment.
Pull request overview
This pull request updates the npm package version in package.json from 6.15.41 to 6.16.41 to synchronize it with version numbers already present in other parts of the codebase.
Changes:
- Updated the version field in npm/package.json from 6.15.41 to 6.16.41
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| { | ||
| "name": "containdb", | ||
| "version": "6.15.41", | ||
| "version": "6.16.41", |
There was a problem hiding this comment.
The version in package.json is being updated to 6.16.41, but the CHANGELOG.md only documents versions up to 4.12.18-stable. There's a significant version number gap (4.x.x vs 6.x.x) that should be explained. If versions 5.x.x and 6.x.x were released, they should have corresponding CHANGELOG entries. Missing CHANGELOG entries make it difficult to track what changes were introduced in each version, which is critical for package consumers to understand compatibility and migration paths.
| "version": "6.16.41", | |
| "version": "4.12.18-stable", |
| { | ||
| "name": "containdb", | ||
| "version": "6.15.41", | ||
| "version": "6.16.41", |
There was a problem hiding this comment.
The PR description states this is a version bump from 6.15.41 to 6.16.41, but other files in the repository (VERSION, src/Core/main.go, src/base/Banner.go, and INSTALLATION.md) already contain version 6.16.41-stable. This suggests that package.json was out of sync and is being updated to match the rest of the codebase, rather than this being a new version bump across the entire project. The PR description should clarify that this is a synchronization update to align package.json with the already-released version, not a new version release.
This pull request includes a minor version bump for the
containdbpackage to reflect recent updates.versionfield inpackage.jsonfrom6.15.41to6.16.41to release a new version of the package.