1.10.2

[VisargD]

Description

Upgrade package json version

Motivation

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)

How Has This Been Tested?

• Unit Tests
• Integration Tests
• Manual Testing

Screenshots (if applicable)

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Related Issues

[matter-code-review]

Summary By MatterAI

🔄 What Changed

This PR updates the package version from the previous version to 1.10.2. This appears to be a version bump for a patch release.

🔍 Impact of the Change

This version update will allow users to access the latest patch version of the @portkey-ai/gateway package. As a patch version increment (x.y.Z), this likely contains bug fixes without introducing breaking changes.

📁 Total Files Changed

• package.json: Updated version number from previous to 1.10.2

🧪 Test Added

N/A - Version bump only, no test changes required.

🔒Security Vulnerabilities

N/A - No security vulnerabilities detected in this version update.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)

How Has This Been Tested?

• Manual Testing

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes

Caution

Package Vulnerabilities

Package	Version	Severity	CVE	Fix Version	Vulnerability
@hono/node-server	^1.3.3		CVE-2024-32652	1.10.1	@hono/node-server has Denial of Service risk when receiving Host header that cannot be parsed
@hono/node-server	^1.3.3		CVE-2024-23340	1.4.1	@hono/node-server cannot handle "double dots" in URL
rollup	^4.9.1		CVE-2024-47068	4.22.4	DOM Clobbering Gadget found in rollup bundled scripts that leads to XSS

Tip

Quality Recommendations

1. Consider adding a CHANGELOG.md entry to document what changed in this version

2. Include release notes in the PR description to help users understand what's new

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant NPM as NPM Registry
    participant Users as Package Users

    Dev->>Dev: Update version in package.json
    Note over Dev: Change version from previous to 1.10.2
    Dev->>NPM: Publish @portkey-ai/gateway v1.10.2
    NPM->>Users: Make v1.10.2 available for installation
    Users->>NPM: npm install @portkey-ai/[email protected]
    NPM->>Users: Deliver updated package

Loading

[matter-code-review]

This PR looks good as it's a simple version bump to 1.10.2. I have no code changes to suggest.