Update changelog for 0.9.1 release (#345)

Author: fohrloop

docs/source/changelog.md

@@ -1,10 +1,13 @@
 # Changelog
 
-## wakepy 0.10.0
-🗓️ Unreleased
+## wakepy 0.9.1
+🗓️ 2024-06-04
 
 ### 🐞 Bug fixes
 - The [SetThreadExecutionState](#windows-stes) Method may now have multiple modes (same or different) activated within the same python thread without them interfering with each other on activation or deactivation, as wakepy creates a *separate worker thread* for the single purpose of setting and keeping the thread execution flag each time you activate a mode with the `SetThreadExecutionState` wakepy.Method. ([#342](https://github.com/fohrloop/wakepy/pull/342))
+- Importing wakepy (0.8.0 and 0.9.0) messed up logging. In particular, the logging level was changed to WARNING due to direct call to `logging.debug()` instead of `logger.debug()`. ([#344](https://github.com/fohrloop/wakepy/pull/344)). Thanks to [@reidswanson](https://github.com/reidswanson) for reporting it.
+- 👷 Fixed running the dev command `inv test` on Windows ([#339](https://github.com/fohrloop/wakepy/pull/339), [#341](https://github.com/fohrloop/wakepy/pull/341))
+
 
 ## wakepy 0.9.0.post1
 🗓️ 2024-06-01

docs/source/methods-reference.md

@@ -85,7 +85,7 @@ Since this method prevents sleep, screen can be only locked automatically if a s
 - **Modes**: [`keep.running`](#keep-running-mode), [`keep.presenting`](#keep-presenting-mode)
 - **Introduced in**: wakepy 0.1.0
 - **How it works**: It calls the [SetThreadExecutionState](https://learn.microsoft.com/en-us/windows/win32/api/winbase/nf-winbase-setthreadexecutionstate) function from the Kernel32.dll with ES_CONTINUOUS and ES_SYSTEM_REQUIRED flags when activating [`keep.running`](#keep-running-mode) mode, and additionally ES_DISPLAY_REQUIRED flag when activating [`keep.presenting`](#keep-presenting-mode) mode. It then uses the ES_CONTINUOUS flag for deactivating.
-- **Wakepy specialities**: Note that as of wakepy 0.10.0 you can have multiple modes (same or different) activated within the same python thread without them interfering with each other on activation or deactivation, as wakepy creates a *separate worker thread* for the single purpose of setting and keeping the thread execution flag each time you activate a mode with the `SetThreadExecutionState` wakepy.Method.
+- **Wakepy specialities**: Note that as of wakepy 0.9.1 you can have multiple modes (same or different) activated within the same python thread without them interfering with each other on activation or deactivation, as wakepy creates a *separate worker thread* for the single purpose of setting and keeping the thread execution flag each time you activate a mode with the `SetThreadExecutionState` wakepy.Method.
 - **Multiprocess safe?**: Yes
 - **What if the process holding the lock dies?**: The lock is automatically removed.
 - **How to check it?**: Run `powercfg /requests` in an elevated cmd or Powershell.