invalid extension version in custom cfconfig is ignored when the extension is bundled

yup, 5.4 won’t be changed, 6.2 is close to the final RC,

now is a really great time to test your code base with 6.2 which is 50% faster than 5.4 for a lot of aspects, helping us catch any remaining bugs

slight follow up for this the reporting of errors with invalid extensions, isn’t quite working as expected

Thanks for checking . To clarify, you can install non-bundled versions of bundled extensions via the LUCEE_EXTENSIONS env variable, .cfconfig, or /deploy - but all of that was only fixed in 6.1. Is that correct? Nothing in 5.4*, nothing still waiting for 6.2?

oops, specified the extension version wrong in the test

this is indeed fixed in 6.1

solution is to upgrade, Lucee 5.4 is in maintenance mode

We already have coverage for installing newer extensions via /deploy and .CFConfig which both work with 6.1

I’ve added a test checking via Lucee extensions, this is still unresolved

as per below, Lucee 6.2 reports installing both the bundled newer and the older version

I'll have to check, I think it might be fixed in 6.1