Schema validation failed: Need rollback support for collection schema changes

Schema Validation Failure

When a Postman collection is imported, the tool validates the JSON against the declared schema URL. If the schema version is unsupported, the import aborts with the error message "Schema validation failed", and the collection is not added to the workspace.

The schema property is treated as immutable within the Postman UI; attempts to edit it directly result in an immediate validation error. Consequently, once a collection has been upgraded to a newer schema, there is no built‑in mechanism to downgrade it back to a previous, supported version. Users must manually edit the JSON file or revert to a prior commit in version control, which is error‑prone and not automated.

Unresolved Decision

Given the lack of automatic downgrade support, it is unclear whether Postman will introduce a feature that safely rolls back a collection to an earlier schema version or expose an API to programmatically change the schema field.

To guide future development, we need to understand the feasibility and implications of such a feature.

Specific Questions

• Will Postman provide a dedicated UI or API endpoint to downgrade a collection’s schema field to a supported older version?
• If not, what safeguards are recommended for users who need to revert schema changes without corrupting the collection?
• How does the current immutability of the schema field affect automated CI/CD pipelines that rely on collection imports?