Note the Major release number being incremented! This means there is a breaking change in this release (yes, the first time so far).
Also note the addition of the CHANGELOG.md file in the repo, where all release changes will be logged, starting with this release!
The breaking change is as follows. sasdata2dataframe (sd2df or other aliases), has returned None when the SAS Data Set provided doesn't exist. Of course, trying to use that as a dataframe results in an exception. But, if you coded a check for this and conditionally didn't use it, then this change will break that code. A FileNotFoundError exception is now thrown, as that's the appropriate Pythonic thing to do in this situation.
If you happened to code this:
df = sas.sd2df('table','libref')
if df is None:
# do something because the data set wasn't found in the SAS session
Then you would need to change that to:
try:
df = sas.sd2df('table','libref')
except FileNotFoundError:
# do something because the data set wasn't found in the SAS session
There is another change that I had to make for the log4j problems. If you recently used the new 'log4j' configuration key in the pervious release, you may need to update the value. SASPy V3.7.8 had log4j 2.12.2 and 2.16.0 jars, but now 2.12.4 and 2.17.1 are included instead.
So, if you happened to use log4j='2.16.0', you need to change that to log4j='2.17.1' in this release. Be aware that this can continue to change if more vulnerabilities are found and fixed in log4j.
Note also that none of the vulnerabilities are exposed by SASPy as it doesn't use log4j, so there's no actual problem with these regardless of their version.