@@ -143,6 +143,10 @@ Changelog
1431430.32.0 (Unreleased)
144144===================
145145
146+ Documentation for breaking changes era on the side of the caution and likely
147+ overstates the risk on many of these. If you are not accessing zeroconf internals,
148+ you can likely not be concerned with the breaking changes below:
149+
146150* BREAKING CHANGE: zeroconf.asyncio has been renamed zeroconf.aio (#503) @bdraco
147151
148152 The asyncio name could shadow system asyncio in some cases. If
@@ -201,6 +205,19 @@ Changelog
201205 These functions are not intended to be used by external
202206 callers and the API is not likely to be stable in the future
203207
208+ * BREAKING CHANGE: Prefix cache functions that are non threadsafe with async _ (#724) @bdraco
209+
210+ Adding (`zc.cache.add ` -> `zc.cache.async_add_records `), removing (`zc.cache.remove ` ->
211+ `zc.cache.async_remove_records `), and expiring the cache (`zc.cache.expire ` ->
212+ `zc.cache.async_expire `) the cache is not threadsafe and must be called from the
213+ event loop (previously the Engine select loop before 0.32)
214+
215+ These functions should only be run from the event loop as they are NOT thread safe.
216+
217+ We never expect these functions will be called externally, however it was possible so this
218+ is documented as a breaking change. It is highly recommended that external callers do not
219+ modify the cache directly.
220+
204221* TRAFFIC REDUCTION: Add support for handling QU questions (#621) @bdraco
205222
206223 Implements RFC 6762 sec 5.4:
@@ -237,6 +254,10 @@ Changelog
237254
238255* MAJOR BUG: Fix queries for AAAA records (#616) @bdraco
239256
257+ * Fix cache handling of records with different TTLs (#729) @bdraco
258+
259+ * Rename handlers and internals to make it clear what is threadsafe (#726) @bdraco
260+
240261* Fix ServiceInfo with multiple A records (#725) @bdraco
241262
242263* Synchronize time for fate sharing (#718) @bdraco
0 commit comments