v3.0.0

Updating FoundationExtensions (breaking change, dropped runtimeWarning in favor of swift-report-issue package)

v2.0.1

What's Changed

• fix promise order as before by @OguzYuuksel in #17

Full Changelog: v2.0.0...v2.0.1

v2.0.0

• Migrate update promise type.

v1.0.0

• Dependency update
• Swift 6 migration

v0.1.17

Changes crash (assert) in URLSessionMock to URLError.Code.cancelled.

v0.1.16

• Update FoundationExtensions versioning.

v0.1.15

Update FoundationExtensions dependency

v0.1.14

Update FoundationExtensions dependency

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.

ValidStatusCode in Publisher extension

Merge pull request #9 from teufelaudio/ValidStatusCode

Added valid status code func to Publisher extension