1.11.0

[VisargD]

Description

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.11.0 in the package.json file.

🔍 Impact of the Change

This version bump indicates a minor release with new features according to semantic versioning. The change will affect how the package is identified in npm and by dependent projects.

📁 Total Files Changed

• package.json: Updated version number to 1.11.0

🧪 Test Added

N/A - This is a version bump that doesn't require specific tests.

🔒 Security Vulnerabilities

N/A - No security vulnerabilities were introduced or addressed in this change.

Type of Change

• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• 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
• Unit Tests
• Integration Tests

Screenshots (if applicable)

N/A

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

N/A

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 release notes or a changelog entry to document what new features or changes are included in version 1.11.0

2. Update any version references in documentation files to match the new version

Tanka Poem ♫

Version increments,
Gateway evolves silently,
One-one-one-zero,
AI flows through new channels,
🚪 Portkey opens wider.

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant NPM as NPM Registry
    participant Deps as Dependent Projects
    
    Dev->>Dev: Update version to 1.11.0 in package.json
    Dev->>NPM: Publish package with new version
    NPM-->>Dev: Confirm publication
    Deps->>NPM: Request @portkey-ai/gateway
    NPM-->>Deps: Provide version 1.11.0

Loading

[matter-code-review]

This PR contains a straightforward version bump from the previous version to 1.11.0, indicating a minor release with new features according to semantic versioning. The change looks good and follows standard package versioning practices.