In regards to (Versions 7.0 through 20.0 of the Salesforce Platform SOAP, Bulk, and REST APIs are currently unsupported and you need to take action before May 2022). We are trying to determine exactly what needs to be changed inside our managed package. From our perspective this doesn't have to do with the <apiVersion>20.0</apiVersion> which resides in the meta.xml file of the class/trigger/object but rather if our code internal/external is using one of the services with an old version EX: a javascript button is using an sforce.connection and the is it using /services/data/20.0/ /services/Soap/ajax/20.0/ .
Based on this https://help.salesforce.com/s/articleView?id=000351312&type=1
We believe this should NOT cause us any problems from our perspective but we want clarification this is the case. Does anyone have any insight into this?
<?xml version="1.0" encoding="UTF-8"?>
<ApexClass xmlns="http://soap.sforce.com/2006/04/metadata">
<apiVersion>20.0</apiVersion>
<status>Active</status>
</ApexClass>
Manoj Nambirajan (Dell Technologies) 
Forum Ambassador
custom apex classes, VF pages or components API versions (even if part of managed package) are out of scope. If you have any components which is of lower api version and has a WSDL behind it. you need to fix those.
otherwise this announcement is mainly for API integrations and its versions
