diff --git a/CHANGELOG.md b/CHANGELOG.md
index c53422ce..9e5ee260 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,34 @@
 
 
 
+## [5.1.0] - 2023-04-14
+
+### Added
+
+-   `Enhancement` Viya has been evolving since I first introduced the HTTP Access Method to connect to SAS w/in Viya (SAS Compute Server). The current versions are configured with TLS (SSL) by default, and there are different ways the system can be configu
+red for this. SASPy uses the Public REST API to interact with Viya. This means HTTPS communication and than means CA Certificates both server side and client side. The best approach with the latest Viya is to configure it with your companies CA Certificate
+s that are already in use on your clients. But, if using Viya generated certificates, then these need to be distributed and installed in the right places on all client machines (that'sa easier said than done). For this case, I've added a new Configuration 
+Definition key, `cafile`, which can be used to specify the location of the Viya Certificate bundle (the path to that .pem file), so that HTTP from python will use this certificate to create a Trusted connection. This access method has had the `verify` key 
+to control whether the connection is to be verified or not (Trusted). With Verify set to True, it now fails if the connection cannot be verified. If False it doesn't try to create a verified connection, same as before. The default it still to try and if no
+t verifiable, fall back to unverified; same as it has been, since the original Viya certificates were not CA Verifiable.
+
+### Changed
+
+-   `Tweak` Update readme and correct typo by @BrokenStreetlight in https://github.com/sassoftware/saspy/pull/538
+
+### Fixed
+
+-   `None` Nothing fixed
+
+### Removed
+
+-   `None` Nothing removed
+
+## New Contributors
+* @BrokenStreetlight made their first contribution in https://github.com/sassoftware/saspy/pull/538
+
+
+
 ## [5.0.2] - 2023-03-10
 
 ### Added