1.12.2

[VisargD]

Description

Release v1.12.2

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]

Description

Summary By MatterAI

🔄 What Changed

The package.json file was modified to update the project version from 1.12.1 to 1.12.2.

🔍 Impact of the Change

This is a minor version increment, indicating a patch, bug fix, or small non-breaking enhancement. It primarily affects dependency management and release tracking, with no direct functional impact on the application's runtime behavior based on this change alone.

📁 Total Files Changed

• package.json: Version updated from 1.12.1 to 1.12.2.

🧪 Test Added

N/A - No new tests were added as this change is a version bump.

🔒Security Vulnerabilities

N/A - This change does not introduce or fix any direct security vulnerabilities.

Motivation

N/A

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?

N/A

• Unit Tests
• Integration Tests
• Manual Testing

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

.

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
hono	^4.6.10		CVE-2025-59139	4.9.7	Hono has Body Limit Middleware Bypass
rollup	^4.9.1		CVE-2024-47068	4.22.4	DOM Clobbering Gadget found in rollup bundled scripts that leads to XSS

Tanka Poem ♫

Version number ascends,
Tiny patch, a new release.
Code base now refined,
Dependencies align with ease,
Science of progress, serene. 🚀

Sequence Diagram

sequenceDiagram
    participant Developer
    participant PackageJson as package.json
    
    Developer->>PackageJson: Update version from 1.12.1 to 1.12.2
    PackageJson-->>Developer: Version updated

Loading

[matter-code-review]

Version bump from 1.12.1 to 1.12.2