Merge branch 'release_4.5' into release_4.6

Author: kriszyp

docs/developers/applications/caching.md

@@ -36,8 +36,8 @@ class ThirdPartyAPI extends Resource {
 Next, we define this external data resource as the "source" for the caching table we defined above:
 
 ```javascript
-const { MyTable } = tables;
-MyTable.sourcedFrom(ThirdPartyAPI);
+const { MyCache } = tables;
+MyCache.sourcedFrom(ThirdPartyAPI);
 ```
 
 Now we have a fully configured and connected caching table. If you access data from `MyCache` (for example, through the REST API, like `/MyCache/some-id`), Harper will check to see if the requested entry is in the table and return it if it is available (and hasn't expired). If there is no entry, or it has expired (it is older than one hour in this case), it will go to the source, calling the `get()` method, which will then retrieve the requested entry. Once the entry is retrieved, it will be saved/cached in the caching table (for one hour based on our expiration time).

docs/technical-details/release-notes/4.tucker/4.5.12.md

@@ -1,6 +1,7 @@
 ### HarperDB 4.5.12
 7/9/2025
 
+- Fix for dynamically setting `harperdb` package symlink on deploy
 - Assign shard numbers from each node's config rather than from routes
 - Handle certificates without a common name, falling back to the SANs
 - Properly clean up blobs that are only transiently used for replication