Problem/Motivation
Hi!
When i opened https://www.drupal.org/project/http_client_manager/issues/3446808 I did not notice the 'old' branch is 9.x and the new one is 3.x; any Drupal "available update" page was not recognizing the 3.1.1 release as the version number is lower and it should not go backwards, although it is a newer version. My bad.
Proposed resolution
Therefore, in order to reestablish the proper functionality of the 9.x branch, #3446808 should be reverted and 9.3.12 released making it compatible again with ^9.4 (though unsupported versions); we can also flag 9.3.11 to not be installed
Then, 3.x branch should be renamed to 10.x, as the number is higher and then the "available update" pages can pick the proper version number if 9.x is installed; with a 10.0.0 release (that can be the same as 3.1.1); no need to push code but just create a new release. With that, the "available updates" page and composer can pick the newest version being only D10 compatible.
| Comment | File | Size | Author |
|---|---|---|---|
| #8 | http_client_manager_update.png | 13.99 KB | gorkagr |
Issue fork http_client_manager-3451503
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #2
gorkagr commentedComment #4
gorkagr commentedI have pushed the code to revert 3446808.
Then the only tasks remaining are:
- to merge and do a new release on 9.x so people using the module are not affected
- maybe flag as unsecure 9.3.11 (apologies)
- and to rename 3.x branch to 10.x so the versioning is higher, making a 10.x release
Comment #5
gorkagr commentedComment #7
aronne commentedWhat a mess guys :)
Anyway I think everything should be ok now.
Let me know if it's working for you as well.
Regards,
aronne.
Comment #8
gorkagr commentedyeah, all seems good now.
9.3 should be back to be compatible with old drupals (sorry one more time) anow the newer version appears to be installed
Comment #9
achtonThanks for this, appreciated!