MySQL 5.7.29 includes the following InnoDB changes:

Not applicable to MariaDB Server

Bug #29195848 ASSERTION "!OTHER_LOCK" IN LOCK_REC_ADD_TO_QUEUE
While the assertion resembles the one in MDEV-15326, this change appears to be totally unrelated to that. It is yet another follow-up to a change that we intentionally skipped in MariaDB Server in MDEV-20850 and MDEV-19342, because the original problem was partly fixed in MDEV-17073 (and later fully fixed in MDEV-17614).

Bug#30324703 : BACKPORT 29942556 TO 5.7
This is something specific to the encryption implementation of MySQL 5.7, which was motivated by the introduction of encryption in MariaDB 10.1. MariaDB manages the encryption keys in a different way.

Bug#30190199 - ERROR WHEN IMPORTING TABLESPACE WITH DIFFERENT DATA DIRECTORY LACKS DETAILS
Ever since MDEV-12488, MariaDB already ignores any mismatch of a DATA DIRECTORY clause when importing tablespaces. The flag in .ibd files is basically treated as garbage, because it does not affect the format of the data file in any way. The MySQL fix will refuse such import, but slightly improve the error message. Our error messages were improved in MDEV-16851.

Applicable to MariaDB Server

Bug#30342846 : N_EXT CALCULATION IS NOT CORRECT WHICH CAUSES WRONG RECORD SIZE CALCULATION
Filed as MDEV-21511.

Bug#30113362: BTR_CUR_WILL_MODIFY_TREE() IS INSUFFICIENT FOR HIGHER TREE LEVEL
Filed as MDEV-21509.

Bug #30287668 INNODB: A LONG SEMAPHORE WAIT
Filed as MDEV-21512.

Bug#29454828 ASSERTION ON IMPORT VIA TRANSPORTABLE TABLESPACE
(follow-up fix to avoid uninitialized variable)
This is improving the error handling for corrupted pages during ALTER TABLE…IMPORT TABLESPACE. The test case does not really seem to cover the fix.
Filed as MDEV-21513.

Bug #30499288 - GCC 9.2.1 REPORTS A NEW WARNING FOR OS_FILE_GET_PARENT_DIR
Simple and innocent-looking change. I have not noticed such a warning for MariaDB on GCC 9.2.1, but this change should not hurt.