After code inspection (which was written by a previous member in our organization) I did update the certes library to version 3.0.4 (https://github.com/fszlin/certes), however I am not sure if I need to take further steps to avoid facing an issue on Feb 8th. Is there a possibility to test this before Feb 8th? Or would one of you nice people know if this library version update is sufficient? I did set the preferred chain parameter to "ISRG Root X1" on the certes generate call as well.
I'm not familiar with certes specifically, but if you're already using the chain rooted in ISRG Root X1 then I'd expect that you'd be all set. All that will be changing in February is which chain is the default.
I have checked the code in question. There is no call to the certes download method as the certificate is fetched when calling the certes generate method, where I can also specify the preferred chain. Do you know if this is sufficient? Many thanks for your help.