Since the schema version of modules is stored in the key-value storage, it is unique to each site and is not synced through configuration management. That makes sense, since updates may need to make adjustments that are not encapsulated in config (such as database updates), but there are other changes that may also be included in config (e.g. adding a new config value).
- Are there any risks to running config import and database updates in either order?
- What is the preferred order for running those operations?
- Do update hooks need to make any special accommodations for config items that may have already been imported?
- Are there any other operations that may be required to fully update the production environment?