Version increments should distinguish discovery file updates from feature updates #2119
Labels
next major: breaking change
this is a change that we should wait to bundle into the next major version
type: feature request
‘Nice-to-have’ improvement, new feature or different behavior or design.
Milestone
Today the minor version number is incremented for both true code changes (big fixes, new features) and routine updates to the API discovery docs.
Ideally the version increment would reflect which of these is changing. My suggestion would be to increment patch number (the 0 in 1.86.0) on discovery file only updates and reserve minor version increments for true code changes.
The text was updated successfully, but these errors were encountered: