v0.1.11

• Migrated to Swift 5.10
• Dependencies updated

v0.1.10

• Update FoundationExtensions versioning.

v0.1.9

Update FoundationExtensions

v0.1.8

Update FoundationExtensions

Link FoundationExtensions statically

Making FoundationExtensions the static default.

Renamed static / dynamic, make sure that packages without any suffix are static. This unifies a inconsistency in a lot of frameworks used in our products. Also, static linking is is an attempt to fix this issue while deploying to TestFlight / AppStore:

ITMS-90334: Invalid Code Signature Identifier. The identifier "FoundationExtensions-5555494443d5626ab868338a93cce6b274e34595"
in your code signature for "FoundationExtensions" must match its Bundle Identifier "FoundationExtensions"

This fixes SwiftUI previews in Swift Packages as well.

FoundationExtensions is the default now, the dynamic product is FoundationExtensionsDynamic.

NWEndpoint allows NetService Publisher injection

For the sake of tests and also in order to customise the way NetServicePublisher is created (for example, providing a custom timeout for address resolution), the NWEndpoint now asks for a NetServicePublisher factory closure in its init so we can decide how the creating will be. The expected Publisher doesn't have to be NetServicePublisher, just match same Output and Failure, which allow testability by injecting Subjects, for example.

More SPM Product options

v0.1.5

Add SPM Product AllStatic (#8)

Remove dependency from LongPolling

v0.1.4

Update NetworkExtensions to get rid of long polling dep (#7)

Make types great again

v0.1.3

Extracted proper type for the service description (#6)

The "fix the broken build" release

v0.1.2

Fix build. Looks like NetworkExtensions still are needed... (#5)