Upgrading Drupal

So far I have been upgrading my Drupal site from 8 to 9 to 10 successfully.

However I could not upgrade it from 10 to 11 because my shared hosting has MariaDB 10.5, while D11 requires 10.6.

So my question is, is it somehow (by overriding or even by hacking the core) possible to make D11 work on MariaDB 10.5?... so that I can go ahead with this upgrade at the moment and wait for the hosting to upgrade MariaDB at a later date.

Please let me know.

Thanks

-Mahesh

Hello everyone,

I'm currently working on updating my Drupal website, but I've encountered some challenges that I hope you can help me with. I've run composer outdated and found a long list of outdated packages that need updating, including Drupal core and several contributed modules. Here are some specifics:

Hi. I'm using Olivero as base theme, and it looks CSS changes after minor upgrading from 10.1 to 10.3.

The mobile menu's icon color seems to be changed from white to black. Is it normal?

When core is minor upgraded, what kind of things are drastically changed? Are there official page for the rule?

Thanks.

I updated Drupal Core from 10.1.8 to 10.3.5. I'm using sub-theme originated from Olivero.

Just after updated, I opens my website and browser's console has error like below:

For navigation-utils.js?v=10.3.5:147:16, having Uncaught TypeError: Cannot read properties of null (reading 'classList')

Any ideas?

[Solved]

https://www.drupal.org/project/drupal/issues/3474666

I did hardcoding js file of the core theme of Olivero below:

Composer outdated "drupal/*" lists some drupal/core- things after running composer update. I updated drupal from 10.1.8 to 10.3.5.

drupal/core-composer-scaffold 10.3.5 11.0.4 A flexible Composer project scaf...
drupal/core-project-message   10.3.5 11.0.4 Adds a message after Composer in...
drupal/core-recommended       10.3.5 11.0.4 Core and its dependencies with k...

Anyideas?

Do I have to solve this, then how? Or is it OK to leave them alone?

[Solved]
The numbers are the virsions of core, so it depends on it.

I have been made aware that Drupal 10.3.3 is requires  twig/twig ~v3.10.2, and it is not possible to install twig v3.14.0 that fixes CVE-2024-45411.

Is there any work-around for this problem?