Question on module update logic

Created on 25 November 2015, almost 9 years ago
Updated 2 August 2023, about 1 year ago

When I ran Available Updates on a 8.0.0 build, the various DEV build modules receive update suggestions for the "RECOMMENDED VERSION", instead of the latest DEV build. If one agrees to an update, the "RECOMMENDED VERSION" is installed. This makes DEV updates from the GUI impossible. I find this counter-intuitive and certainly counterproductive.

Is this the module update logic that is actually desired? How about giving the user a choice between updating to a later build of the "INSTALLED VERSION" and the "RECOMMENDED VERSION"?

✨ Feature request
Status

Closed: duplicate

Version

9.5

Component
UpdateΒ  β†’

Last updated about 9 hours ago

  • Maintained by
  • πŸ‡ΊπŸ‡ΈUnited States @tedbow
  • πŸ‡ΊπŸ‡ΈUnited States @dww
Created by

πŸ‡ΊπŸ‡ΈUnited States platinum1

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024