This is mainly a communication problem, but you can make errors less likely by some simple technical and organizational measures. First, you should provide a well, high quality documentation of all the entries in your configuration files, as well as some easily accessible example or "default" configuration file. The example file can be automatically deployed to each environment, since it is not intended to be changed by the prod team directly.
Next, with each new release, provide a changelog, where important changes are documented. Changes to the configuration which could prevent the system from working when they are missing are always important, so make sure the information is there.
For example, lets say dev team adds a few key-value pairs to application.properties in their environment. What would be the best way to record these new keys, so that when the deployment occurs in the ops team they know exactly which keys to add, so the risk of starting the new service and seeing it failed because of a missing key is minimized ?
The best way to reduce the risk of failing is to avoid changing your application in a way it requires the new keys, so the application should be backward compatible to older configuration files whenever possible. Often, your application can behave in a sensible way by providing inbuilt default values for the new keys for the case they are missing.
However, if that is not possible, your system should make it as easy as possible for the prod team to find out why the new service fails to start when the key is missing. There should be clear error message, telling exactly which key is missing in which file, and if necessary where to find the information about the missing key, or a hint or example about a meaningful entry for this key.
If the configuration is complex, and the format changes in a way manual editing becomes error prone, you might also consider to provide tools for editing the configs and for migration to a newer version.
For example, I am using the Firefox web browser, and with each new release (which I get automatically), certain things are added to the local configuration one can inspect on the "about:config" page. This is comparable to the config in your "production" environment. Since the whole configuration is kept strictly backward compatible, I never have to add new keys to the config manually just because a there is a new release of the browser. And for the case I want to change something there (maybe a new entry which was not part of the previous version), I either use the Tools/Options menu, or the "about:config" page, and can find the entry plus some kind of documentation. So I recommend trying to implement your system in a comparable way.