[wp-meta] [Making WordPress.org] #1034: api.wordpress.org/plugins/update-check/1.1/ enhancement

[Making WordPress.org]

#1034: api.wordpress.org/plugins/update-check/1.1/ enhancement
--------------------------+-------------------------------
Reporter:  brettshumaker  |      Owner:
    Type:  enhancement    |     Status:  new
Priority:  normal         |  Component:  api.wordpress.org
Keywords:                 |
--------------------------+-------------------------------
 Just want to open a discussion about the way we're checking for
 plugin/theme updates. Consider the situation where a user has a plugin
 with a version of `1.02` and the developer building the plugin realizes
 that s/he should be using semantic versioning so they release an update
 with a version of `1.1.0`. Makes sense, right? A young developer is trying
 to correct a mistake they did, but WordPress doesn't behave "logically"
 and does not trigger an update for users of the plugin. The only course of
 action the developer has in this instance is to issue another update to
 their plugin with a version of at least `1.2.0`, which could be confusing
 for the end user.

 Currently the API uses `version_compare()` and I feel like the issue could
 be solved by instead using `strnatcmp()`. I'm sure it's been done this way
 for a long time and I was not involved with WordPress when the initial
 decision was made to use `version_compare()` but can anyone think of any
 instances where `strnatcmp()` would fail at recognizing a newer version of
 a plugin/theme in the repository?

 Thanks!

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/1034>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org