Breaking change in v2.3-RC2

[testower]

As raised in slack earlier in the week.

What is the issue and why is it an issue?

I noticed there is a breaking change in v2.3-RC2, in vehicle_types.json, name in the conditional requirement of the new field "default_pricing_plan_id":

“REQUIRED if both system_pricing_plans.json and vehicle_types.json are defined.”

We are unable to complete implementation of this release candidate until this is solved.

Please describe some potential solutions you have considered (even if they aren’t related to GBFS).

The field should be made optional, and a conditional requirement can be added in v3.

Is your potential solution a breaking change?

• Yes
• No
• Unsure

[mplsmitch]

Thanks for Flagging this @testower - I'm updating the release candidate, should be completed sometime on Monday 3/28. I'll update this issue when the corrected release candidate is ready.

[mplsmitch]

This change has been incorporated into v2.3-RC2 along with other minor corrections