Release 1.9.3.11:
- New sections "postponing_start" and "postponing_end" in INI file.
  These work in the same way as corresponding booking sections (booking_start / booking_end). However, unlike the booking sections, postponing actions do not support passing booking data as an argument.

Release 1.9.3.10:
- New sections "booking_start" and "booking_end" in INI file. You can configure local executables (e.g. .exe, .bat or .ps1), which should be run when a booking either starts or ends.
  You can define settings for path, arguments, working directory and if the window should be hidden. There is a special argument for passing the current booking data. See examples in IrisUserAgent.ini.sample.
- Updated all referenced libraries to the newest version. Chromium Embedded Framework remains at v123.0.60 for now (due to IDE integration dependencies, and required sandbox integration in newer versions).

Release 1.9.3.9:
- Improved exception handling when calling API - InvalidOperationException should show more details.
- When testing the connection in the agent settings, the actual API URL is also taken into account (not only the Base URL).

Release 1.9.3.8:
- When the agent is reset by provider admins using the "Release" button (or ending the session using the systray menu), the next bookings are handled correctly now.
  Previously, authentication did not trigger for the next booking if no misuse policy with early arrival was configured for the resource.
- The agent could not be reset multiple times in a row, and incorrectly displayed the warning "There is no active session.". This issue has now been fixed.

Release 1.9.3.7:
- Allow provider admins to reset the agent directly from the session clock, even when no booking is active. The "Release" button is now visible.
  Previously, the session clock displayed no information or button, making it difficult to re-initiate authentication and request a new booking if required.

Release 1.9.3.6:
- Sometimes postponing on the lock screen was prevented when a new authentication request started. It has been fixed (missing reset of information about last active session).
- Small visual improvement for the session clock - additional padding for the timer (only visible in light mode).
- Prevent repeated warning about early arrival (if outside of allowed time range). Warnings are now limited to once every five minutes.
- If a provider admin has authenticated for a booking of a different user, it is reflected in the session clock.
  The timer is not running and there is a "Release" button instead of "End Session". When releasing the session, the authentication for the current booking is initiated again.
- The automatic transition to the next booking, where the user matches the provider admin, now works if the admin has already authenticated for the current booking, regardless of the user associated with that booking.