Closed jenlampton closed 3 years ago
I'm getting the same thing with a local copy of the site, so there's something in the code that's triggering this. I suspect it's the "Auto-merge conflicts" feature on Pantheon and not actually our upstream, but I'd still love to know where to look if anyone has any pointers :)
I did a grep through my codebase for "1.4.2" and found a handful of .info files with packaging information in them. I don't know when that got there, but I was able to replace all those .info files with versions that did not have the packaging info, and Backdrop now knows it's up to date.
My pantheon site is very confused. I used the Pantheon dashboard to update to 1.18.1, it applied all the updates for me (I did need to use the "auto resolve conflicts button" but now Backdrop believes its running version 1.4.2.
The status report page shows 1.18.1 as the current version, but also shows that a security update is available.
The available updates page, however, reports the core version as 1.4.2.
Bootstrap reports the correct version: