[Louayzouaoui1]

Summary

Fixes skillRegistry.resolveVersion for >=, <= and == constraints (src/lib/skills/registry.ts). The operator was read with constraint.charAt(0), so ">=1.0.0" became operator ">" against base "=1.0.0", whose major parses to NaN, and no version ever satisfied it. The ">=", "<=" and "==" cases in the switch were unreachable.

The operator is now matched with /^(>=|<=|==|\^|~|>|<)/ (two-character operators first) and the base version is the rest of the string. Constraints without an operator still fall through to the exact-version match, and single-character operators behave as before.

Related Issues

• Closes skills: resolveVersion never matches >=, <= or == constraints (operator parsed with charAt(0)) #16186

Validation

• Change type: other (skills registry)
• Focused tests: node --import tsx/esm --import ./open-sse/utils/setupPolyfill.ts --import ./tests/_setup/isolateDataDir.ts --test --test-force-exit tests/unit/skills-resolve-version.test.ts tests/unit/skills-executor.test.ts tests/unit/skills-injection.test.ts tests/unit/skills-marketplace.test.ts (24 pass, plus tests/unit/characterization-skills.test.ts)
• eslint and prettier --check on the changed files
• Based on the tip of release/v3.8.52
• Production-code change includes a new automated test in this PR

Tests Added Or Updated

• Added tests/unit/skills-resolve-version.test.ts: >=, <= and == (match and no-match cases), plus a case pinning that >, <, ^, ~ and exact versions are unchanged. The three new-operator tests fail without the fix and pass with it.
• Updated tests/unit/characterization-skills.test.ts: the characterization test for this bug now asserts the corrected behaviour.
• Added the changelog fragment changelog.d/fixes/0000-skills-resolve-version-operators.md.

Coverage Notes

• resolveVersion operator parsing is covered by the new test file.

Reviewer Notes

• test(characterization): fix the public surface of memory, guardrails, skills, a2a and oauth before the v4 extraction (rail 3.8.55) #16179 pinned the old behaviour in characterization: resolveVersion with >=, <= or == constraints currently never matches. I flipped that test in this PR (renamed, with the corrected expectations), as skills: resolveVersion never matches >=, <= or == constraints (operator parsed with charAt(0)) #16186 asked.
• I didn't run the full unit suite or npm run lint locally; CI runs them.

[diegosouzapw]

Hi @Louayzouaoui1 — closing this pull request to clear the open queue. The branch fix/skills-resolve-version-operators is kept, so the commits stay. Comment here if it should be reopened.

[diegosouzapw]

Hi @Louayzouaoui1 — reopening this pull request. The close was a mistake, and it is back in the merge queue. The branch fix/skills-resolve-version-operators was kept.