Drush now tries to update from 1.10 to 2.16. However, reading the project page it clearly says "do not upgrade from 1 to 2. It will break your layouts and configuration.".
What happened to the 1.x version?
I see no post or explanation why it was removed.
Is the recommendation to simply lock the version to 1.10?

Comments

eric-addcream created an issue. See original summary.

grossmann’s picture

grossmann commented

Same problem here. I get security warnings in my update reports because v. 1.10 is now longer found.
Updating to 2.x is no option as it would destroy the layouts of the whole site (as stated in the module description).

dmclark84’s picture

dmclark84 commented
Related issues: +#2983825: Security Update 7.x.-1.x -> 7.x-2.x

I am guessing it is related to this issue from over a year ago and the 7.x-1.x is marked as unsupported.

https://www.drupal.org/project/ds/issues/2983825

fenstrat’s picture

fenstrat
he/him
Primary language English
Location Australia
commented

Looks like 7.x-1.10 contained the same fix as 7.x-2.15 which addressed https://www.drupal.org/sa-contrib-2018-019

Give there's been no further security releases it isn't clear why 7.x-1.x was marked as unsupported?

ymdavoust’s picture

ymdavoust commented

If indeed there are no security issues with 7.x-1.10, could this version be marked as supported again ? Thanks!

grossmann’s picture

grossmann commented

I would also be happy if the 7.x-1.10 would be marked as supported again until a security issue for this version appears.
This would prevent the false positive report emails.

jackalope’s picture

jackalope commented

Same concerns here. Is the 7.x-1.x branch actually no longer being supported? If it isn't supported anymore, that's a separate concern, since future security issues will no longer be addressed. But the current situation makes it seem like there's a required security update available for 7.x-1.x sites, which isn't true.

radio_babylon’s picture

radio_babylon commented

can someone PLEASE fix this? im managing a number of legacy sites that cant update to 2.x and the security warning message is making people freak out.

pefferen’s picture

pefferen commented

Is there something we, from the community, can do to help move this issue forward?

aspilicious’s picture

aspilicious commented
Status: Active » Closed (won't fix)

It's marked as unsupported because it's deprecated 7,5 years ago when 7.2 got released.
You can update to version 2 but it needs a bit of reconfiguration of the displays.

I think we can mark something as unsupported after 7 years?
And yes if there is no security update you just can lock the version on 7.10.