chore(main): release 3.3.0 (#79)

🤖 I have created a release *beep* *boop*
---


##
[3.3.0](3.2.0...3.3.0)
(2024-05-31)


### Features

* adds ability to provide a OSLog instance via the Config.logger
property
([c10ec29](c10ec29))
* adds ability to provide a OSLog instance via the Config.logger
property
([#78](#78))
([2220929](2220929))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

chore(main): release 3.2.0 (#73)

🤖 I have created a release *beep* *boop*
---


##
[3.2.0](3.1.1...3.2.0)
(2023-12-29)


### Features

* Add Compilation & Testing On Windows
([#68](#68))
([ac5f18c](ac5f18c))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

---------

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: LaunchDarklyReleaseBot <LaunchDarklyReleaseBot@launchdarkly.com>

prepare 3.1.1 release (#60)

## [3.1.1] - 2023-06-12
### Fixed:
- Per the SSE spec, an HTTP 204 will now halt retry attempts by default.

prepare 3.1.0 release (#52) (#58)

## [3.1.0] - 2023-06-05
### Changed:
- Enforce TLS v1.2 as a required minimum.

### Fixed:
- Fix re-entrancy issue with `start` command. (Thanks,
[g-mark](#56)!)

prepare 3.0.0 release (#52)

## [3.0.0] - 2022-10-06
### Changed
- Dropped support for older versions in accordance with the new [Xcode 14 release](https://developer.apple.com/documentation/xcode-release-notes/xcode-14-release-notes).

prepare 2.0.0 release (#49)

Merge pull request #43 from launchdarkly/release-1.3.1

Prepare 1.3.0 release (#40)

## [1.3.0] - 2022-01-18
### Added
- Added the configuration option `urlSessionConfiguration` to `EventSource.Config` which allows setting the `URLSessionConfiguration` used by the `EventSource` to create `URLSession` instances.

### Fixed
- Fixed a retain cycle issue when the stream connection is ended.
- Removed deprecated `VALID_ARCHS` build setting from Xcode project.
- Unterminated events will no longer be dispatched when the stream connection is dropped.
- Stream events that set the `lastEventId` will now record the updated `lastEventId` even if the event does not generate a `MessageEvent`.
- Empty stream "data" fields will now always record a newline to the resultant `MessageEvent` data.
- Empty stream "event" fields will result in now result in the default "message" event type rather than an event type of "".

Prepare 1.2.1 release (#19)

## [1.2.1] - 2021-02-10
### Added
- [SwiftLint](https://github.com/realm/SwiftLint) configuration. Linting will be automatically run as part of the build if [Mint](https://github.com/yonaskolb/Mint) is installed.
- Support for building docs with [jazzy](https://github.com/realm/jazzy). These docs are available through [GitHub Pages](https://launchdarkly.github.io/swift-eventsource/).

### Fixed
- Reconnection backoff was always reset if the  previous successful connection was at least `backoffResetThreshold` prior to the scheduling of a reconnection attempt. The connection backoff has been corrected to not reset after the first reconnection attempt until the next successful connection. Thanks to  @tomasf for the PR ([#14](#14)).
- On an `UnsuccessfulResponseError` the configured `connectionErrorHandler` would be called twice, the second time with a `URLError.cancelled` error. Only if the second call returned `ConnectionErrorAction.shutdown` would the `EventSource` client actually shutdown. This has been corrected to only call the `connectionErrorHandler` once, and will shutdown the client if `ConnectionErrorAction.shutdown` is returned. Thanks to  @tomasf for the PR ([#13](#13)).
- A race condition that could cause the eventsource to restart after shutting down has been fixed.

Merge pull request #11 from launchdarkly/release-1.2.0

Prepare 1.2.0 release