Update to social-11.11.0 went backwards from social-11.10.2 to social-11.10.x.dev

Problem/Motivation

I attempted to update yesterday from social-11.10.2 [released on October 4] to social-11.11.0 [released on October 10] but instead the result reverted to social-11.10.x-dev [which was released on July 13].

I did so by changing my composer.json to "goalgorilla/open_social": "~11.11.0", (other settings: "minimum-stability": "dev", and "prefer-stable": true,) and running # composer update -W

The release notes for 11.11.0 say:

On this version... We have released the branch 11.11.x and this version (11.11.0) as there were some inconsistencies in the code concerning update hook numbering and our version 12 in regards to preparing to be Drupal 10 compatible. Those changes were all backwards compatible so no need to release them only in version 12.

This release contains bugfixes, new features and Drupal 10 compatibility updates that are backwards compatible.

Can anyone suggest what causes this backwards update?

No dependency issues were reported when running # composer update -W --dry-run or # composer update -W so I am baffled why this backward update took place!

Steps to reproduce

1. Take a distribution of Open Social social-11.10.2
2. Modify composer.json to "goalgorilla/open_social": "~11.11.0",
3. Run: # composer update -W

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes