The compareMultiSemver function now uses the embedded compareSemver

[vim-zz]

function instead of importing it from an external file.

… compareMultiSemver git:(embed-compare-semver-in-multi-plugin  node index.js
✓ Test 1 passed: compareMultiSemver([["1.2.3", "1.2.1"], ["1.3.1", "1.2.3"]]) === "minor"
✓ Test 2 passed: compareMultiSemver([["1.2.3", "0.2.1"], ["1.3.1", "1.2.3"]]) === "major"
✓ Test 3 passed: compareMultiSemver([["2.2.3", "0.2.1"], ["1.3.1", "1.2.3"]]) === "major"
✓ Test 4 passed: compareMultiSemver([["1.2.3", "1.2.1"], ["1.2.4", "1.2.3"]]) === "patch"

🎉 All tests passed!

✨ PR Description

Purpose: Embed compareSemver functionality directly into compareMultiSemver plugin to eliminate external dependency and improve maintainability.
Main changes:

• Integrated compareSemver function code directly into compareMultiSemver module
• Removed external dependency on compareSemver module
• Enhanced test cases with better error messages and success confirmation output

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀}

[orca-security-us]

Orca Security Scan Summary

Status	Check	Issues by priority
Passed	Infrastructure as Code	0   0   0   0	View in Orca
Passed	SAST	0   0   0   0	View in Orca
Passed	Secrets	0   0   0   0	View in Orca
Passed	Vulnerabilities	0   0   0   0	View in Orca

[gitstream-cm]

✨ PR Review

The PR successfully embeds the compareSemver function to eliminate external dependency, but introduces test code in the production file and has potential issues with semver comparison logic.

2 issues detected:

🧹 Maintainability - Test code should not be part of production modules as it creates unnecessary coupling and potential runtime overhead.

Details: The file now contains test cases and console output statements that are executed as part of the main module. This makes the production code noisy and couples testing logic with business logic.
File: plugins/filters/compareMultiSemver/index.js

🐞 Bug - Using character codes for version comparison can lead to incorrect semantic version ordering.

Details: The convertPart function uses charCodeAt() to convert alphabetic characters to numeric values, which can create inconsistent ordering for prerelease versions. Character codes vary significantly (a=97, z=122) leading to unexpected comparison results.
File: plugins/filters/compareMultiSemver/index.js (55-56)

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using. We'd love your feedback! 🚀}

[gitstream-cm]

🐞 Bug - Inconsistent Prerelease Handling: Implement proper semver prerelease comparison logic or use a standardized approach for handling alphabetic version suffixes instead of character codes.

Suggested change

	const match = /[A-Za-zαß]/.exec(x);
	return Number(match ? x.replace(match[0], "." + x.charCodeAt(match.index)) : x);
	const match = /^(\d+)([A-Za-zαß]*)$/.exec(x);
	if (!match) return Number(x);
	const numeric = Number(match[1]);
	const alpha = match[2];
	if (!alpha) return numeric;
	// Convert alphabetic suffix to a small decimal increment for proper ordering
	// Each character contributes progressively smaller values to maintain order
	let alphaValue = 0;
	for (let i = 0; i < alpha.length; i++) {
	const charValue = alpha.charCodeAt(i) - 96; // normalize a=1, b=2, etc.
	alphaValue += charValue / Math.pow(100, i + 1); // decimal fractions
	}
	return numeric + alphaValue;