Repository navigation
chore: set version to 2.3.8 - #73
Merged
Merged
Conversation
development was at 2.3.9 while the last published version on npm is 2.3.7 and master is at 2.3.8 (never published). Set development to 2.3.8 so the next release is a single patch on top of 2.3.7. Only package.json and package-lock.json change (version fields). Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
reeshika-h
approved these changes
Nov 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Sets the package version on
developmentto2.3.8, so the next release is a single patch on top of the last published version.Why
latest2.3.7master2.3.8(never published)development(before this PR)2.3.92.3.8came from an earlier Snyk-fix PR and was never released, and a later Snyk fix bumpeddevelopmentto2.3.9. Releasing2.3.9would skip a version on npm. Settingdevelopmentto2.3.8keeps the next release at2.3.7→2.3.8.Changes
package.json:version2.3.9→2.3.8package-lock.json: the twoversionfields2.3.9→2.3.8No dependency or source changes.
npm ciworks against the lock file, and2.3.8is greater than the latest tagv2.3.7, socheck-version-bumpshould pass.🤖 Generated with Claude Code