Possibly incorrect react experimental rollback

[AdrienLemaire]

What Renovate type, platform and version are you using?

Describe the bug
Got 2 renovate PRs to rollback react & react-dom

Package	Type	Update	Change
react (source)	dependencies	rollback	0.0.0-experimental-4ead6b530 -> 0.0.0-experimental-3310209d0
react-dom (source)	dependencies	rollback	0.0.0-experimental-4ead6b530 -> 0.0.0-experimental-3310209d0

Reverting broke my tests with numerous errors:

Minified React error #170; visit https://reactjs.org/docs/error-decoder.html?invariant=170 for the
full message or use the non-minified dev environment for full errors and additional helpful warnings.

Checking the react github repo and commit logs, I cannot find any mention of a revert needed, and I cannot even find the commit which hash starts with 331020.
Why is this rollback done, and what is is rollbacking to ?

To Reproduce

setup a package.json with

    "react": "0.0.0-experimental-4ead6b530",
    "react-dom": "0.0.0-experimental-4ead6b530",

renovate has then created the PR to rollback to 3310209d0

[rarkins]

The way these experimental versions are done is a misuse of semver, and they will be sorted as per semver guidelines. It's hard to tell what is the correct one to be using because you can't sort commit hashes, but here's the current tagging:

Here's the recent list of published versions:

I suggest you utilize followTag and set it to "experimental" for the react page (use a package rule to configure it).

[AdrienLemaire]

@rarkins thanks for the reply!

I actually already have the followTag.

[
    {
      "followTag": "experimental",
      "ignoreUnstable": false,
      "packageNames": [
        "react",
        "react-dom",
        "react-router",
        "react-router-dom"
      ]
    }
  ]

If I understand correctly, the PR message was misleading because it's not a rollback but an upgrade. And I need to fix my repo.
Indeed, I can verify that at https://www.npmjs.com/package/react.
Looks like the react team's use of git tag is not reliable.

Thanks!

[rarkins]

I guess what happened is:

• Renovate has correctly detected/followed the right "version"
• It calculates that the new version is less than the current version so classifies it as a rollback.