CHANGES.md in ruby-jss-3.2.0b3 vs CHANGES.md in ruby-jss-3.2.0b4

@@ -15,10 +15,20 @@
 Many many thanks to actae0n of Blacksun Hackers Club for reporting this issue and providing examples of how it could be exploited.
 
 --------
 ## \[UNRELEASED] 
 
+### Added 
+  - Several new attributes to Jamf::Computer instances: 
+    - `#enrolled_via_ade?` Boolean
+    - `#mdm_capable?` Boolean
+    - `#supervised?` Boolean
+    - `#user_approved_enrollment?` Boolean
+    - `#user_approved_mdm?` Boolean
+    - `#mdm_profile_expiration` Time
+
+
 ### Changed
   - Improved handling of known API bug in Jamf::Scopable::Scope.  
 
     There is a long-standing bug in working with 'scope' via the Classic API, which can cause data-loss when you have 'Users' and 'User Groups' (known in the api data as `jss_users` and `jss_user_groups`) defined in the targets or exclusions. Thanks to @yanniks on GitHub, I recently learned that the bug only affects a few API objects, namely Policies and PatchPolicies.  
 
@@ -43,10 +53,11 @@
 
     For more details, see the discussion in the comments/docs for the Jamf::Scopeable::Scope class in lib/jamf/api/classic/api_objects/scopable/scope.rb or in the [rubydocs page for the Scope class](https://www.rubydoc.info/gems/ruby-jss/Jamf/Scopable/Scope).  
 
 
 ### Fixed
-  - Jamf::DeviceEnrollment.device no longer uses String#upcase!, which fails on frozen strings. Instead just use String#casecmp?
+  - `Jamf::DeviceEnrollment.device` no longer uses String#upcase!, which fails on frozen strings. Instead just use String#casecmp?
+  - `Jamf::APIConnection::Token#account` now returns an instance of `Jamf::OAPISchemas::AuthorizationV1` 
 
 ## \[3.1.0] 2023-06-06
 
 ### Added
   - Jamf::Computer.filevault_info and Jamf::Computer#filevault_info can retrieve FileVault info from v1/computer-inventory/filevault and related endpoints