You can now strictly validate version numbers with the Open Commerce API (OCAPI). OCAPI requests that include a version number with leading zeros, such as v024_05, are rejected. These requests return a 400 Bad Request response and an InvalidVersionException fault. Going forward, if you have a new project or a major refactoring, use the B2C Commerce API (SCAPI) instead of OCAPI.
Where: This change applies to B2C Commerce.
How: Contact your B2C Commerce support representative to turn on strict validation. Update your integrations to remove leading zeros from version numbers before enabling the feature.