1.9.18

[VisargD]

Description

Release v1.9.18

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]

Important

PR Review Skipped

PR review skipped as per the configuration setting. Run a manually review by commenting /matter review

💡Tips to use Matter AI

Command List

• /matter summary: Generate AI Summary for the PR
• /matter review: Generate AI Reviews for the PR
• /matter release-notes: Generate AI release-notes for the PR
• /matter <ask-question>: Chat with your PR with Matter AI Agent
• /matter remember <recommendation>: Generate AI memories for the PR

[matter-code-review]

Summary By MatterAI

🔄 What Changed

Version bump from 1.9.17 to 1.9.18 in package.json for the @portkey-ai/gateway package.

🔍 Impact of the Change

This is a minor version update that will affect package versioning when published to the NPM registry. No functional code changes are included in this PR.

📁 Total Files Changed

1 file changed with 1 line added and 1 line deleted.

🧪 Test Added

N/A - Version bump only, no functional changes requiring tests.

🔒Security Vulnerabilities

N/A - No security implications from version change.

Motivation

Version bump for new release of the Portkey AI gateway.

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
• 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

Sequence Diagram

sequenceDiagram
    Developer->>package.json: Update version
    Note over package.json: Version changed from 1.9.17 to 1.9.18
    package.json-->>NPM Registry: Will be published with new version

Loading