postman-collection-transformer lacks a conversion path from v2.0 to v2.1

[sanjayrajesh]

I’m trying to convert a Postman Collection from schema v2.0.0 to v2.1.0 using the transformer’s CLI/programmatic API, but it fails with Unable to convert the input: Error: no conversion path found. The stack trace points to converters/index.js:100, which implies there’s no registered path from 2.0 to 2.1 even though the transformer does have support for v1.0 → v2.1.0. I need the transformer to handle 2.0 → 2.1 as well, but that path isn’t available, so I have to work around it manually.

Steps to reproduce

1. Install postman-collection-transformer globally (npm install -g postman-collection-transformer).
2. Run the CLI or programmatic transformer.convert with inputVersion: "2.0.0" and outputVersion: "2.1.0" using any valid v2.0 collection.
3. Observe the error: no conversion path found.

Expected behavior
The transformer should either provide a direct conversion path from Postman v2.0 to v2.1, or at least convert via an intermediate v1.0 → v2.1 path without throwing no conversion path found. That way consuming code can upgrade legacy v2.0 collections without custom workarounds.

Environment

• node 24.12.0
• postman-collection-transformer (latest)
• CLI or programmatic usage that specifies inputVersion: "2.0.0" and outputVersion: "2.1.0".

Let me know if you need example collections or logs; I can share the JSON I tested with.