Swiftpack.co - Swift Packages by apple

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - ControlNet - Speed improvements to Swift.package scheduler and tokenizer code Initial release

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Minor - `EmbeddedChannel`: `getOption(ChannelOptions.allowRemoteHalfClosure)` should not `fatalError` (#2429) ### SemVer Patch - Pooled control message storage. (#2422, patch credit to @ser-0xff) - NIOPOSIX happy eyeballs now hops to the connection event loop when using a custom resolver to avoid data races (#2436) ### Other Changes - Add tests for WebSocketMaskingKey.random() (#2433, patch credit to @gwynne) - Add narrative documentation for NIO's concurrency bridges (#2423) - Include relevant versions (kernel & Swift) in test output (#2425) - Update `update-alloc-limits-...` script (#2430) - Fix flaky test in NIOAsyncWriter (#2431) ### SemVer Minor - addition of assertSuccess() and assertFailure() on EventLoopFuture (#2417, patch credit to @dkz2) ### SemVer Patch - Tolerate sending data after close(mode: .output) (#2421) ### SemVer Minor - Add CustomDebugStringConvertible conformance to ByteBuffer (#2418, patch credit to @gwynne) - Add unprocessedBytes property on NIOSingleStepByteToMessageProcessor (#2419) ### SemVer Patch - Handle close(output) in the pipeline handler. (#2414) - NIOThrowingAsyncSequenceProducer throws when cancelled (#2415) ### Other Changes - Add `AsyncChannel` based `ServerBootstrap.bind()` methods (#2403) - Extend the integration test harness to track FDs (#2411) - AsyncChannelBootstrapTests bind to 0 instead (#2412, #2413) ### SemVer Minor - Drop Swift 5.5 (#2406) ### SemVer Patch - Handle reentrant reads in ALPNHandler (#2402) - Close accepted FDs if we fail to create Socket (#2407) - Don't have channels stop reading on errors they tolerate. (#2408) ### Other Changes - Add docker-compose file for Swift 5.9 (#2404) - Fix broken docs. (#2405) - Avoid double-closing on fcntl failures (#2409) ### SemVer Minor - Add `NIOAsyncChannel` as SPI (`@_spi(AsyncChannel)`) (#2397) - Throw `CancellationError` if `NIOThrowingAsyncSequenceProducer.AsyncIterator.next()` is cancelled instead of returning `nil`. The user defined generic `Failure` type of `NIOThrowingAsyncSequenceProducer` is also deprecated and must now always be `any Swift.Error`. (#2399, #2401) ### SemVer Patch - Mildly rework the NIOLock storage (#2395) ### Other Changes - Update links in NIO docs index (#2396) - Clean up and regression check the docs. (#2400) ### SemVer Minor - Mark EventLoop.syncShutdownGracefully and EventLoopGroup.syncShutdownGracefully noasync (#2381) - Add a pooled recv buffer allocator (#2362) - NIOAsyncWriter: Provide a fast path for single element writes (#2365) - Provide OnLoopSendable: Sendable containers that bind a value to a specific EventLoop (#2370) - Add support for UDP_SEGMENT (#2372) - Add support for UDP_GRO (#2385) ### SemVer Patch - Pool buffers for ivecs and storage refs in the event loop. (#2358, patch credit to @ser-0xff) - Fix memory binding. (#2376, patch credit to @ser-0xff) - Fix an upcoming compiler warning on implicit raw pointer casts. (#2377, patch credit to @atrick) - Buffer pool for message headers and addresses. (#2378, patch credit to @ser-0xff) - Remove unused array (#2361) - Make PooledBuffer safer. (#2363) - Fix swift-nio iOS builds. (#2369) - Don't retain a task when all we want is a time (#2373) - Make our time types transparent (#2374) - Allow UDP GRO tests to fail in some circumstances (#2387) ### Other Changes - TCP channel throughput benchmark. (#2367, patch credit to @ser-0xff) - Add UDP performance tests (#2360) - Clarify on EL semantics (#2366) - Add availability requirements to TCPThroughputBenchmark (#2368) - Not Holding OnToRunClosure() test updates (#2375) - Remove redundant availability guards (#2379) - Lower the max segment count in tests (#2382) - Rebuild the channel when retrying testWriteBufferAtGSOSegmentCountLimit (#2383) - Rework the `NIOAsyncSequenceProducer` tests to rely less on timings (#2386) - Work around the SwiftPM layout change. (#2389) - Always populate utsname (#2391) ### SemVer Minor - Special case EventLoopPromise.succeed() when Value is Void (#2311, patch credit to @mob-connection) ### SemVer Patch - Tail allocate mutex and a generic value using ManagedBuffer (#2349, patch credit to @asdf-bro) ### Other Changes - Add Swift 5.8 CI and update nightly CI to Ubuntu 22.04 (#2350) - Lift alloc counter Package.swift to 5.1 and add platforms (#2352) - Point docs to Swift Package Index (#2353) - Fix flaky testTaskCancel_whenStreaming_andNotSuspended (#2355) ### SemVer Patch - Remove useless instance variables in the SelectableEventLoop (#2338, patch credit to @thomas-gill-0xff) - Repair the Windows build of NIOCore (#2339, patch credit to @compnerd) - Allow writing and reading empty datagrams (#2341, patch credit to @hashemi) - Prepare mmsghdr structure properly. (#2346, patch credit to @ser-0xff) - Implement `remoteAddress0` and `localAddress0` on `EmbeddedChannel` (#2345) ### Other Changes - Fix main nightly CI (#2337) - 2023 is real, we should support it (#2342) - Avoid actually allocating a giant buffer (#2347) - Avoid integer literals that won't fit. (#2348) ### SemVer Minor - Add `NIORawSocketBootstrap` (#2320, #2317) - Make EventLoopFuture.wait() unavailable from async (#2331) - Add easier async to future conversion (#2334) ### SemVer Patch - Cap read+pread POSIX read sizes at Int32.max (#2323) - Fix non Darwin/Linux builds (#2328) - Remove implicit ByteBuffer copy in copyMemory (#2330) ### Other Changes - Remove `_NIOBeta` product (#2319) - Remove obsolete information from the README (#2321) - Add .spi.yml for Swift Package Index DocC support (#2324, #2329) - Measure allocations applying WS mask (#2333) - Improve performance of tests (#2336)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Swift Algorithms is now source stable! ### Changes - Most sequence and collection types have been renamed, following a more consistent naming structure: - The `Lazy` prefix was dropped. - Either a `Sequence` or `Collection` suffix was added depending on whether or not the type is unconditionally a collection. - The base name was derived from the name of the method that produces it, including an argument label to disambiguate if necessary. - Types that can only be produced from a lazy sequence chain now unconditionally conform to `LazySequenceProtocol` and wrap the base sequence instead of the lazy wrapper, making some return types slightly simpler. - e.g. `[1, 2, 3].lazy.reductions(+)` now returns `ExclusiveReductionsSequence<[Int]>`, not `ExclusiveReductionsSequence<LazySequence<[Int]>>`. - The generic parameters of the `ExclusiveReductions` type have been swapped, putting the base collection first and the result type second. - The `Indices` associated type of `IndexedCollection` now matches `Base.Indices`. ### Removals - Previously deprecated type and method names have been removed: - The `Chain` type alias for `Chain2Sequence` - The `chained(with:)` method which was replaced with the `chain(_:_:)` free function - The `LazyChunked` and `Chunked` type aliases for `ChunkedByCollection` - The `rotate(subrange:at:)` and `rotate(at:)` methods which were renamed to `rotate(subrange:toStartAt:)` and `rotate(toStartAt:)` respectively ### Fixes - The `StridingSequence` and `StridingCollection` types now conditionally conform to `LazySequenceProtocol`, allowing the `striding(by:)` method to properly propagate laziness in a lazy sequence chain. - Fixed `chunked(by:)` to always compare two consecutive elements rather than each element with the first element of the current chunk. (#162) ### Additions Expanded versatility for two existing operations: - A series of `joined(by:)` overloads concatenate a sequence of sequences using an element or a collection, either passed in or generated from consecutive elements via a closure. (#138) - Additional `trimming(while:)` methods for trimming only the start or end of a collection, as well as mutating versions of all three variants. (#104) ### Additions Two new additions to the list of algorithms: - `adjacentPairs()` lazily iterates over tuples of adjacent elements of a sequence. (#119) - `minAndMax()` finds both the smallest and largest elements of a sequence in a single pass. (#90) ### Changes - When calling `chunked(on:)`, the resulting collection has an element type of `(Subject, SubSequence)` instead of just `SubSequence`, making the subject value available when iterating. ```swift let numbers = [5, 6, -3, -9, -11, 2, 7, 6] for (signum, values) in numbers.chunked(on: { $0.signum() }) { print(signum, values) } // 1 [5, 6] // -1 [-3, -9, -11] // 1 [2, 7, 6] ``` ### Fixes - Improvements to the documentation and PR templates. ### Fixes - `Product2` associated type inference error in release build (#130) ### Additions - The `compacted()` method lazily finds the non-`nil` elements of a sequence or collection (#112). ### Changes - The `uniqued()` method now lazily computes the unique elements of a sequence or a collection (#71). Pass this resulting sequence to an `Array` initializer to recover the behavior of the previous release. - Calling `cycled(times:)` now returns a new `FiniteCycle` type, which has the same conformances as its underlying collection (#106). - The base collections of the sequence and collection wrapper types are no longer public (#85, #125), and the wrapper types no longer conform to the `Equatable` or `Hashable` protocols (#124). If you need those conformances, convert the wrapper type to an `Array` or other collection currrency type before storing. Please file an issue if these changes pose a problem for your use case. ### Additions More new algorithms to join the party: - A lazy version of the standard library's two `split` methods. (#78) - `firstNonNil(_:)` returns the first non-`nil` element from an optional-generating transform. (#31) - `uniquePermutations()` skips duplicates when generating permutations of a collection. (#91) - The `reductions` methods return all the in-between states of reducing a sequence or collection. (#46) ### Fixes - Methods and computed properties are more consistently marked as inlinable, resolving a performance regression. - The `Stride` type now efficiently calculates distances between positions, supported by the underlying collection. - Better test coverage and improved diagnostics for comparing sequences. - Fixed links and improved documentation. ### Additions An exciting group of new algorithms, contributed by the community: - `trimming(while:)` returns a subsequence of a bidirectional collection with the matching elements removed from the start and end. (#4) - `min(ofCount:)` and `max(ofCount:)` find the smallest or largest elements in a collection. (#9, #77) - `windows(ofCount:)` lets you iterate over all the overlapping subsequences of a particular length. (#20) - `striding(by:)` iterates over every *n*th element of a sequence or collection. (#24) - `interspersed(with:)` places a new element between every pair of elements in a sequence or collection. (#35) - `chunks(ofCount:)` breaks a collection into subsequences of the given number of elements. (#54) - `suffix(while:)` matches the standard library's `prefix(while:)`, by returning the suffix of all matching elements from a bidirectional collection. (#65) - Variations of `combinations(ofCount:)` and `permutations(ofCount:)` that take a range expression as a parameter, returning combinations and permutations of multiple lengths. (#51, #56) ### Changes - The `LazyChunked` type now precomputes its `startIndex`, making performance more predictable when using the collection. ### Fixes - `randomSample(count:)` no longer traps in rare circumstances. - Index calculations have been improved in a variety of collection wrappers. - A variety of documentation improvements and corrections. ### Changes - The `rotate(at:)` method has been updated to `rotate(toStartAt:)`, with the old name deprecated. - The `chained(with:)` method has been changed to the free function `chain(_:_:)`, with the old version deprecated. - `Algorithms` now uses `RealModule` from the `swift-numerics` package for its cross-platform elementary functions. - Sequence/collection wrapper types, like `Permutations` and `Indexed`, now have conformance to the lazy protocols, so that any following operations maintain their laziness. ### Fixes - Swift Algorithms now builds under SwiftPM on Windows. - A wide variety of errors, misspellings, and ommissions in the documentation and guides have been fixed. - Index/distance calculations for the `Product2` and `Chain` types have been corrected. - Calling `stablePartition(subrange:by:)` now correctly uses the subrange's length instead of the whole collection. Initial release.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ## What's Changed * Pull a few updates to the 1.x branch by @thomasvl in https://github.com/apple/swift-protobuf/pull/1384 * 2GB limits on delimited decode * Reading of delimited data in chunks for better performance/error handing * Update 1.x podspec to work with Xcode 14.3 by @bnickel in https://github.com/apple/swift-protobuf/pull/1403 * Bump version for a 1.22.0 release. by @thomasvl in https://github.com/apple/swift-protobuf/pull/1404 * Expose implementationOnlyImports option in SPM plugin by @gjcairo in https://github.com/apple/swift-protobuf/pull/1406 ## New Contributors * @bnickel made their first contribution in https://github.com/apple/swift-protobuf/pull/1403 **Full Changelog**: https://github.com/apple/swift-protobuf/compare/1.21.0...1.22.0 ## What's Changed * 1.x branch unknown enums decoding option support by @thomasvl in https://github.com/apple/swift-protobuf/pull/1347 * 1.x branch: Bump the Swift 5.7.0 testing to 5.7.2. by @thomasvl in https://github.com/apple/swift-protobuf/pull/1354 * 1.x branch: Fail to encode google.protobuf.Value number if not finite. by @thomasvl in https://github.com/apple/swift-protobuf/pull/1353 * 1.x branch: Add import paths to SPM Plugin (#1373) by @thomasvl in https://github.com/apple/swift-protobuf/pull/1374 * 1.x branch: Validate length before turning into an Int. by @thomasvl in https://github.com/apple/swift-protobuf/pull/1376 * 1.x branch: bump to 1.21.0 to make a release. by @thomasvl in https://github.com/apple/swift-protobuf/pull/1383 **Full Changelog**: https://github.com/apple/swift-protobuf/compare/1.20.3...1.21.0 * Minor Updates * Be more accepting for generation options. by @thomasvl in https://github.com/apple/swift-protobuf/pull/1318 * Add the file naming option by @thomasvl in https://github.com/apple/swift-protobuf/pull/1338 **Full Changelog**: https://github.com/apple/swift-protobuf/compare/1.20.2...1.20.3 * Minor Updates * For protoc generator authors (swift-grpc), bring over some descriptor improvements to aid migration. by @thomasvl in https://github.com/apple/swift-protobuf/pull/1291 **Full Changelog**: https://github.com/apple/swift-protobuf/compare/1.20.1...1.20.2 * Minor Updates * Provide environment variable configuration option by @FranzBusch in https://github.com/apple/swift-protobuf/pull/1279 * Fix warning in new package.swift by @FranzBusch in https://github.com/apple/swift-protobuf/pull/1281 **Full Changelog**: https://github.com/apple/swift-protobuf/compare/1.20.0...1.20.1 * Major Updates * SPM plugin by @FranzBusch #1276 **Full Changelog**: https://github.com/apple/swift-protobuf/compare/1.19.1...1.20.0 * Minor Updates * Back port negative duration #1260 **Full Changelog**: https://github.com/apple/swift-protobuf/compare/1.19.0...1.19.1 * Major Updates * SwiftWasm compilable #1192 * Sendable conformance on Messages without library changes #1208 & #1213 * Minor Updates * Swift format lint issues #1199 * Visit extensions improvement #1201 (smaller codegen) * Tweak generation for messages with only extension ranges. #1202 (codegen change to help compilation performance) - Minor Updates - Support JSON `ignoreUnknownFields` within WKTs. #1172 - Handle writing out json when the value is empty/zero bytes and no type. #1167 - Fixes from fuzz testing: - Handle skipping a JSON object that ends after the open brace. #1165 - When skipping a varint for an unknown field, ensure it is valid. #1169 - Rework JSON skipping so it's not recursive for nested arrays #1178 - Track recursion depth for nested JSON ListValue structures #1179 - Uses same workaround for stack sizes in non optimized builds. #1183 - Reject fieldmasks that have non-ASCII characters for JSON #1185 - Don't overrun string when parsing timestamps #1186 * Significant Change * `TextFormatDecodingError` has a new error case to got with a recursion limit for TextFormat decoding (add safety found via fuzz testing for potential bogus input trying trigger stack overflow #1132), if you have any `switch` states on all the cases, this is a breaking change in that you must handle the new case. * Fixes from fuzz testing: * Fix octal TextFormat decoding failure #1124 * Avoid walking off the end of the buffer in two parsing cases. #1126 * Add TextFormatDecodingOptions and implement a recursion limit. #1132 * Don't walk off the end of the buffer during a unicode bytes decode. #1136 * Minor Updates * Change `oneof` enforcement to allow null (found via upstream conformance test requirements) #1135 * Allow proto3_optional for extensions. #1138 * Some edge case speed improvements: * Add modify operation to ExtensionFieldValueSet. #1137 * Don't do characterwise-compares if not needed. #1145 * Clear previous contents before decoding Any from TextFormat #1147

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ## Primary change Address too aggressive warning logging on LogHandlers that do not support `MetadataProvider`. The warning would be emitted too frequently, resulting in flooding logs with warnings. Instead, the warning is now emitted once per log handler type. ## What's Changed * Avoid logging warnings when handler does not support metadataproviders by @ktoso in https://github.com/apple/swift-log/pull/252 * Handle providers properly in multiplex log handler by @ktoso in https://github.com/apple/swift-log/pull/254 * Add CI for Swift 5.8 and update nightly to Ubuntu 22.04 by @yim-lee in https://github.com/apple/swift-log/pull/255 **Full Changelog**: https://github.com/apple/swift-log/compare/1.5.1...1.5.2 ## Summary This patch release focuses on minor cleanups to ergonomics of setting metadata providers with the default stream log handlers, and fixes a bug in the default handler not printing the provided extra metadata by default (it does now). Thank you to @slashmo for quickly noticing and providing a patch for the latter! ## What's Changed * Allow passing explicit provider into the stream handlers by @ktoso in https://github.com/apple/swift-log/pull/250 * Emit correct metadata from StreamLogHandler by @slashmo in https://github.com/apple/swift-log/pull/251 **Full Changelog**: https://github.com/apple/swift-log/compare/1.5.0...1.5.1 # Changes ## Swift version support This release drops support for Swift 5.0. Swift 5.1+ remain supported for the time being. ## Logger.MetadataProvider This release introduces metadata providers! They are an additional way to add metadata to your log statements automatically whenever a log statement is about to be made. This works extremely well with systems like distributed tracing, that may pick up trace identifiers and other information from the task-local context from where the log statement is being made. The feature came with a [swift evolution style proposal](https://github.com/apple/swift-log/blob/main/proposals/0001-metadata-providers.md) introduction to the "why?" and "how?" of this feature you may find interesting. Metadata providers are used like this: ```swift import Logging enum Namespace { @TaskLocal static var simpleTraceID: String? } let simpleTraceIDMetadataProvider = Logger.MetadataProvider { guard let traceID = Namespace.simpleTraceID else { return [:] } return ["simple-trace-id": .string(traceID)] } LoggingSystem.bootstrap({ label, metadataProvider in myCoolLogHandler(label: label, metadataProvider: metadataProvider) }, metadataProvider: simpleTraceIDMetadataProvider) ``` which in turn makes every `Logger` on this `LoggingSystem` add this contextual metadata to log statements automatically: ```swift let log = Logger(label: "hello") Namespace.$simpleTraceID.withValue("1234-5678") { test() } func test() { log.info("test log statement") } // [info] [simple-trace-id: 1234-5678] test log statement ``` ### Adoption in `LogHandler`s In order to support this new feature in your log handlers, please make it accept a `MetadataProvider?` at creation, and store it as: ```swift struct MyHandler: LogHandler { // ... public var metadataProvider: Logger.MetadataProvider? // ... } ``` ## What's Changed ### Highlight * Metadata Providers (e.g. for Distributed Tracing) in LogHandlers by @ktoso in https://github.com/apple/swift-log/pull/238 ### Other changes * [docs] Minimal docc setup and landing page by @ktoso in https://github.com/apple/swift-log/pull/226 * =docc Make docs use symbol references by @ktoso in https://github.com/apple/swift-log/pull/230 * =docc Move to multiple Package.swift files by @ktoso in https://github.com/apple/swift-log/pull/231 * Undo 5.7 package files, not needed yet by @ktoso in https://github.com/apple/swift-log/pull/232 * Update README: Add missing Source param by @Rusik in https://github.com/apple/swift-log/pull/233 * Fix build for wasm by @ahti in https://github.com/apple/swift-log/pull/236 * Add .spi.yml for Swift Package Index DocC support by @yim-lee in https://github.com/apple/swift-log/pull/240 * Fixes link to Supabase repository in README.md by @timobollwerk in https://github.com/apple/swift-log/pull/245 ## New Contributors * @Rusik made their first contribution in https://github.com/apple/swift-log/pull/233 * @ahti made their first contribution in https://github.com/apple/swift-log/pull/236 * @timobollwerk made their first contribution in https://github.com/apple/swift-log/pull/245 **Full Changelog**: https://github.com/apple/swift-log/compare/1.4.4...1.5.0 ## Sendable fixup for 1.4.3 The 1.4.3 release carefully introduced `Sendable` across the library; sadly we missed that `5.6.x` Swift series treat a "missing marker protocol conformance for Sendable" as an _error_ while it is intended to be a _warning_ as which it is correctly reported in Swift 5.7. This release fixes this by _not requiring_ that values stored in `Logger.MetadataValue.stringConvertible` must be Sendable, however practically speaking they should be thread-safe in any case, as it is not guaranteed in any way when/where this string convertible value will be invoked from. This release contains no other changes from 1.4.3. ## What's Changed * [sendable] Sendable conformance checks cause errors on 5.6 but warnings on 5.7 by @ktoso in https://github.com/apple/swift-log/pull/229 **Full Changelog**: https://github.com/apple/swift-log/compare/1.4.3...1.4.4 ## Highlights Loggers and all related types are now `Sendable`, including metadata values which have to be Sendable as well. When using from Swift that is concurrency aware, you may be getting warnings where you didn't before, these are all correct though - you need to be ready for e.g. logger metadata to be accessed from another thread. Thankfully values logged this way should usually be sendable to begin with, preferably value types. For more details see: https://github.com/apple/swift-log/pull/218 ## What's Changed * Remove references to Swift 4 by @steipete in https://github.com/apple/swift-log/pull/186 * Include source in StreamLogHandler output by @slashmo in https://github.com/apple/swift-log/pull/189 * Improve StdioOutputStream with fwrite (#180) by @felipejinli in https://github.com/apple/swift-log/pull/188 * use #fileID for Swift 5.3+ by @weissi in https://github.com/apple/swift-log/pull/187 * Add `SwiftLogNoOpLogHandler.init(_: String)` by @glbrntt in https://github.com/apple/swift-log/pull/194 * update 5.4 to release docker image by @tomerd in https://github.com/apple/swift-log/pull/196 * adopt security guidelines by @weissi in https://github.com/apple/swift-log/pull/197 * Logging: avoid a deprecation warning on Windows by @compnerd in https://github.com/apple/swift-log/pull/199 * Tests: enable tests on Windows by @compnerd in https://github.com/apple/swift-log/pull/198 * Add swift-log-elk as a new logging backend to the Readme by @philippzagar in https://github.com/apple/swift-log/pull/201 * Add swift-log-SwiftyBeaver as a new logging backend to README.md by @ShivaHuang in https://github.com/apple/swift-log/pull/203 * fix jazzy issues on older versions of ubuntu by @tomerd in https://github.com/apple/swift-log/pull/210 * add docker setup for 5.5 by @tomerd in https://github.com/apple/swift-log/pull/211 * Android support by @andriydruk in https://github.com/apple/swift-log/pull/209 * update doc generation script by @tomerd in https://github.com/apple/swift-log/pull/213 * Add 5.6 nightly CI by @Lukasa in https://github.com/apple/swift-log/pull/214 * ci update by @tomerd in https://github.com/apple/swift-log/pull/219 * Add binaryscraping/swift-log-supabase to README by @grsouza in https://github.com/apple/swift-log/pull/221 * better abstration for LoggingSystem state by @tomerd in https://github.com/apple/swift-log/pull/222 * adopt sendable by @tomerd in https://github.com/apple/swift-log/pull/218 * minimal DocC markdown to order Logger.Levels by @heckj in https://github.com/apple/swift-log/pull/225 ## New Contributors * @steipete made their first contribution in https://github.com/apple/swift-log/pull/186 * @slashmo made their first contribution in https://github.com/apple/swift-log/pull/189 * @felipejinli made their first contribution in https://github.com/apple/swift-log/pull/188 * @philippzagar made their first contribution in https://github.com/apple/swift-log/pull/201 * @andriydruk made their first contribution in https://github.com/apple/swift-log/pull/209 * @Lukasa made their first contribution in https://github.com/apple/swift-log/pull/214 * @grsouza made their first contribution in https://github.com/apple/swift-log/pull/221 * @heckj made their first contribution in https://github.com/apple/swift-log/pull/225 **Full Changelog**: https://github.com/apple/swift-log/compare/1.4.2...1.4.3 This release fixes a single bug in the propagation of the `function` parameter in the source-less `Logger.trace` function. For more details refer to https://github.com/apple/swift-log/pull/185 - thank you noticing and fixing the issue @saulbaro! You can find additional details on all changes in this release in the [1.4.2 milestone](https://github.com/apple/swift-log/milestone/8?closed=1). This patch release fixes some compatibility issues, including a Windows compatibility issue as well as wrongly removed APIs in the 1.3.0->1.4.0 transition. No new features were added in this release. You can refer to the detailed changes by inspecting the issues linked form the [1.4.1 milestone](https://github.com/apple/swift-log/milestone/7?closed=1). ### Highlights This release addresses a missing `public init` in the newly introduced `NoOpLogHandler`. Please use 1.4.0 rather than 1.3.0 to be able to actually instantiate the that handler. ### SemVer Minor - Add `public init` to `NoOpLogHandler` introduced in 1.3.0 https://github.com/apple/swift-log/pull/142 ### Credits This release contains a single PR: https://github.com/apple/swift-log/pull/146 The complete change-list is available on the [1.4.0 milestone](https://github.com/apple/swift-log/milestone/6?closed=1). Thank you @adam-fowler for spotting and fixing the mistake! ### Highlights **`LogHandler` implementations** should take care adjust their implementations moving forward to implement the following `log` function: ```swift func log( level: Logging.Logger.Level, message: Logging.Logger.Message, metadata: Logging.Logger.Metadata?, source: String, // new (!) file: String, function: String, line: UInt ) ``` rather than the previous function: ```swift func log( level: Logging.Logger.Level, message: Logging.Logger.Message, metadata: Logging.Logger.Metadata?, file: String, function: String, line: UInt ) ``` Compatibility shims are provided and existing implementations will continue to work as-is. However in order to reap benefits of the new `source` (which will contain the "module name from which this log message originates") parameter, they will have to change which `log` overload they implement. We suggest moving to implementing the _new_ overload (with `source:`) as soon as possible, allowing the logging ecosystem to make use of this new capability. For details see: - Add "source" for log messages https://github.com/apple/swift-log/pull/135 ### SemVer Minor - Add "source" for log messages https://github.com/apple/swift-log/pull/135 - Add NoOpLogHandler for when you don't want logging https://github.com/apple/swift-log/pull/142 - Logging: port to Windows https://github.com/apple/swift-log/pull/118 - =multiplex #139 more properly handle logLevel in multiplex handler https://github.com/apple/swift-log/pull/140 - Note that previous behavior of the `MultiplexLogHandler` was very surprising and this change makes it more consistent, see the PR for details if you are using multiplex handlers ### SemVer Patch - silence #file to #filePath warnings https://github.com/apple/swift-log/pull/133 - a number of readme and docs improvements: - docs: =doc #82 avoid showcasing internal lock in public docs https://github.com/apple/swift-log/pull/144 - Fix doc typo #134 - Add more syntax highlighting to the readme file #114 - and more, see the [1.3.0](https://github.com/apple/swift-log/milestone/5?closed=1) milestone for all closed issues. ### Credits This release includes 15 issues/PRs, which were made possible with the help of 18 contributors 🎉 We would like to thank all everyone for their feedback and contributions: Tomer Doron, Johannes Weiss, Konrad `ktoso` Malawski, Saleem Abdulrasool, Gwynne Raskind, prafsoni, Adam Fowler, Neal Lester, Artur Dryomov, Franz Busch, Shiva Huang, zach wick, Ravi Kandhadai, YR Chen, Jeremy Greenwood, Will Lisac, Mattt, Tanner Thank you! ## SemVer Major - Make log levels codable (#99) ## SemVer Minor - docs: remove level parameter from log helpers (#91) - list more logging backends in readme (#95, #92, #88)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### Fixes - Arguments with the `.allUnrecognized` parsing strategy no longer consume built-in flags like `--help` and `--version`. (#550) - Fixes an issue introduced in version 1.2.0 where properties with underscored names couldn't be parsed. (#548) - Improves the error message for cases where platform availability causes the synchronous `ParsableCommand.main()` static method to be run on an `AsyncParsableCommand` type. (#547) ### Changes - Documentation is now primarily hosted at the [Swift Package Index](https://swiftpackageindex.com/apple/swift-argument-parser). ### Fixes - `exit(_:)` no longer causes infinite recursion on the WASI platform. (#520) - Completion scripts for `fish` now provide completions after a non-hyphen-prefixed argument has been provided. (#535) - Overload selection for custom `ExpressibleByArgument` types has been improved. (#522) - The usage string for `.postTerminator` arguments now includes the required terminator (`--`). (#542) - Documentation and testing fixes and improvements. The 1.2.1 release includes contributions from @Chamepp, @kkk669, @mtj0928, @natecook1000, @rauhul, @rickrizzo, @TiagoMaiaL, and @yim-lee. Thank you! ### Additions - You can now provide a title in an `@OptionGroup` declaration. Titled option groups are listed separately in the help screen under that title as a heading. (#492) - Two new parsing strategies have been added for `@Argument` array properties: - `.allUnrecognized` captures all unrecognized inputs after parsing known flags, options, and arguments. - `.postTerminator` collects any inputs that follow the `--` terminator. See the [`ArgumentArrayParsingStrategy` documentation][arrayparse-docs] for more. (#496) - Default values are now supported for `@Argument` or `@Option` properties with optional type, allowing you to initialize those properties with `nil`. Providing a non-`nil` default value results in a warning, since optional properties with non-`nil` defaults don't need to be declared as optionals. (#477, #480) ### Changes - The `.unconditionalRemaining` array parsing strategy has been deprecated and renamed to `.captureForPassthrough`, to better fit its semantic behavior and intended usage. See the [`ArgumentArrayParsingStrategy` documentation][arrayparse-docs] for more. (#496) ### Fixes - Invalid `init(from:)` decoding initializers are now correctly diagnosed by ArgumentParser's validators. (#487) - Default values are now correctly displayed as flags for `@Flag` properties with inversions or `EnumerableFlag` types. (#486) - The help display for non-string-backed raw representable types has been corrected to not show raw Swift values. Instead, the help display uses the type's customized `defaultValueDescription` and `allValues` implementations. (#494) - Properties at different levels of a command hierarchy with the same Swift name but different argument names no longer collide. (#495) - The **`generate-manual`** plugin name is improved when used from within Xcode. (#505) - Documentation fixes and improvements. The 1.2.0 release includes contributions from @allevato, @clayellis, @compnerd, @d-ronnqvist, @natecook1000, @randomeizer, and @rauhul. Thank you! [arrayparse-docs]: https://apple.github.io/swift-argument-parser/documentation/argumentparser/argumentarrayparsingstrategy ### Changes - The **`generate-manual`** plugin now defaults to creating single page manuals. The `--single-page` flag has been replaced with `--multi-page` to restore the previous default functionality. (#472) *Migration:* Update scripts that invoked **`generate-manual`** without `--single-page` to include `--multi-page` and update scripts that invoked **`generate-manual`** with `--single-page` to omit the flag. - The "experimental" prefix from the **`generate-manual`** plugin has been removed. (#475) *Migration:* Update scripts to invoke the **`generate-manual`** plugin via `swift package generate-manual` instead of `swift package plugin experimental-generate-manual`. ### Fixes - The **`generate-manual`** plugin is correctly declared as a product, making the plugin visible to clients. (#456) - The **`generate-manual`** plugin's `--authors` arguments are now correctly passed to the underlying generation tool. (#471) - Manuals generated by the **`generate-manual`** plugin now include the option's value names and do not include value names for flags. (#473) - Built-in flags such as `--help` and `--version` are now correctly marked as optional fixing some generated content which indicated the flags are always required. (#474) - Value descriptions are now correctly derived for types which are `ExpressibleByArgument` and `RawRepresentable` by `String`. Help menus will now display valid default values for such types. (#476) The 1.1.4 release includes contributions from @ian-twilightcoder, @MarcoEidinger, and @rauhul. Thank you! ### Additions - `ArgumentParser` now includes a SwiftPM plugin for generating `man` pages. Explore the functionality and configuration by running `swift package plugin experimental-generate-manual --help` from your package root. (#332) ### Fixes - Hidden subcommands are now excluded from completion scripts. (#443) - When an invalid value is provided for a `CaseIterable` type, the error message now includes a list of valid inputs. (#445) - There's now a diagnostic when an `AsyncParsableCommand` is incorrectly placed under a non-`async` root command. (#436) The 1.1.3 release includes contributions from @keith, @KeithBird, @konomae, @LucianoPAlmeida, and @rauhul. Thank you! ### Changes - CMake builds now always statically link `ArgumentParserToolInfo`. (#424) ### Fixes - When a user provides an array-based option's key (e.g. `--key`) without any values, the error message now correctly describes the problem. (#435) The 1.1.2 release includes contributions from @compnerd and @KeithBird. Thank you! ### Fixes - Moves the platform requirement from the package level down to the new types and protocols with `async` members. This was a source-breaking change in 1.1.0. (#427) - Fixed issues in the CMake build configuration. ### Additions - A command's `run()` method now supports `async`/`await` when the command conforms to `AsyncParsableCommand`. (#404) - New API for distinguishing between public, hidden, and private arguments and option groups, and a new extended help screen accessible via `--help-hidden`. (#366, #390, and [#405 through #413][group]) - You can now override the autogenerated usage string when configuring a command. (#400) ### Changes - `ArgumentParser` now requires Swift 5.5. ### Fixes - The auto-generated usage string now correctly hides all optional parameters when over the length limit. (#416) - One `@Option` initializer now has its parameters in the correct order; the incorrect initializer is deprecated. (#391) - Help flags are now correctly captured in `.unconditionalRemaining` argument arrays. - Documentation fixes and improvements. The 1.1.0 release includes contributions from @keith, @MartinP7r, @McNight, @natecook1000, @rauhul, and @zkiraly. Thank you! [group]: https://github.com/apple/swift-argument-parser/compare/1.0.3...HEAD ### Changes - When a user provides an incorrect value for an option, an `ArgumentParser`-based program now includes the valid values when possible. ``` $ example --format png Error: The value 'png' is invalid for '--format <format>'. Please provide one of 'text', 'json' or 'csv'. ``` ### Fixes - Resolves an issue with `zsh` custom completions for command names that include a dash. - Improves the generated completions scripts for `fish`. - Resolves issues that prevented building `ArgumentParser` for WebAssembly using SwiftWasm toolchains. - Improved window size handling on Windows. - Fixed a crash when using `--experimental-dump-help` with commands that provide non-parsed values. - Fixes an issue where subcommands that declare array arguments with the `.unconditionalRemaining` parsing strategy unexpectedly miss arguments, extending the change in #333 to subcommands. (#397) - Corrects the order of an `@Option` initializer's parameters, deprecating the old version. (#391) - Expanded and corrected documentation. The 1.0.3 release includes contributions from @atierian, @CraigSiemens, @dduan, @floam, @KS1019, @McNight, @mdznr, @natecook1000, @rauhul, and @yonihemi. Thank you! ## Fixes - Addresses an issue when building tests under Mac Catalyst.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This is a documentation update, including the addition of basic DocC documentation bundles. This release has no functional changes. ### Changes - The package now contains documentation bundles, enabling nicer presentation of API documentation in DocC. ### Fixes - #186 [OrderedCollections] Document Sorting as Stable (by @benrimmington) ### Pull requests - #178 [OrderedDictionary] Tiny documentation fix (by @lorentey) - #187 Fix `rethrows` position (by @ensan-hcl) - #189 [OrderedSet] Tiny doc fixes for isSuperset (by @lorentey) - #201 [OrderedCollections] Update docs to state that the sort algorithm is stable (by @lorentey) - #214 [OrderedSet] Small doc updates/fixes (by @lorentey) - #252 [1.0] Add DocC documentation bundles (by @lorentey) **Full Changelog**: https://github.com/apple/swift-collections/compare/1.0.3...1.0.4 Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. This release resolves issues uncovered since 1.0.2 was tagged. The fixes improve performance of some operations, resolve compile-time issues and update documentation. This release contains no observable behavioral changes. ### Changes - [Clutter] When opened in Xcode, the package no longer adds spurious schemes to dependent projects. (#155) ### Fixes - [Build-time issue] Code that is calling `OrderedDictionary`'s uniquing/unique/grouping initializers and merge operations no longer gets flagged as ambiguous in certain cases involving type inference. (#125, #139) - [Build-time issue] The package no longer fails to build when library evolution is enabled. (#157) (Note: this configuration remains unsupported. This package does not provide any guarantees about ABI stability.) - [Performance] In-place mutations of collection contents no longer result in unnecessary heap allocations. (#164) - [Performance] On Swift 5.6 and better, some operations in the `OrderedCollections` module now make use of the stdlib's [temporary allocation facility](https://github.com/apple/swift-evolution/blob/main/proposals/0322-temporary-buffers.md). (#160) - [Docs] Documentation was updated to clarify behavior of the `filter` and `merge` methods of `OrderedDictionary`. (#145) ### Pull requests - #140 [OrderedDictionary] Fix type inference issue with OrderedDictionary.init(grouping:by:) (by @lorentey) - #153 [OrderedDictionary][doc] Update docs for merge/filter operations (by @lorentey) - #155 Remove Swift PM Artifacts to avoid Generated Schemes in Xcode (by @hectormatos2011) - #156 Reinstate custom schemes under Utils/swift-collections.xcworkspace (by @lorentey) - #160 [OrderedCollection] Use standard temp allocation facility, if available (by @lorentey) - #161 [Xcode] Update schemes & file template (by @lorentey) - #162 [OrderedSet] Work around weird name lookup issue in compiler (by @lorentey) - #165 Force-inline _modify accessors to work around a performance issue (by @lorentey) - #169 [OrderedDictionary] Resolve call-site ambiguities (by @lorentey) - #170 Update README for 1.0.3 (by @lorentey) **Full Changelog**: https://github.com/apple/swift-collections/compare/1.0.2...1.0.3 Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. This release resolves issues uncovered since 1.0.1 was tagged, including a high severity crash in `OrderedSet` and `OrderedDictionary`. Upgrading is recommended for all clients. ### Fixes - Fixed a value semantic violation in `OrderedSet` and `OrderedDictionary` that could result in some mutation methods corrupting shared copies of the same value, leading to subsequent crashes. (Issue #104) - `Deque.append(contentsOf:)` now uses an exponential storage resizing strategy, as expected. Calling it in a loop no longer results in O(n) reallocations. (Issue #113) ### Pull requests - #113 [Deque] append(contentsOf:): Use exponential capacity reservation (by @lorentey) - #123 [OrderedSet] Add missing uniqueness check (by @lorentey) - #126 [Utils] run-full-tests.sh: Keep going after a failure (by @lorentey) - #128 [Utils] run-full-tests.sh: Add support for testing on Swift 5.3 without manual editing (by @lorentey) Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. ### Changes - The CMake configuration now supports building the package for AArch64 Linux distributions, unblocking adoption in SPM. (Note that the CMake configuration is intended only to support the use of this package from within Swift toolchain builds. It is provided as is, with no source compatibility guarantees.) - Minor documentation updates. ### Pull requests - #111 [CMake] Match lowercase "aarch64" (by @neonichu) - #112 [OrderedSet][doc] Fix thinko (by @lorentey) Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. This release marks an important milestone for this package -- the advent of source stability! ### Changes - The public API of Swift Collections is now considered source stable. The README defines what we consider public API. - The three `OrderedDictionary` methods that were deprecated in 0.0.7 are now marked unavailable. - `OrderedDictionary.init(uncheckedUniqueElements:)` no longer creates large dictionary instances without an associated hash table. ### Pull requests - #95 Follow stdlib's leading underscore rule (by @ejmarchant) - #96 Documentation: Remove in-place mutation comments (by @ejmarchant) - #97 Freeze some types for consistency with their inlinable initializers (by @lorentey) - #102 1.0 release preparations (by @lorentey) - #106 [OrderedSet] Make _checkInvariants public and call it in more operations (by @lorentey) - #107 [OrderedSet] Don't let the unchecked init create large sets with no hash table (by @lorentey) - #110 [run-full-tests.sh] Fix bashism: == vs = (by @lorentey) Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. This release prepares for source stability by deprecating some OrderedDictionary APIs that we'd like to remove in version 1.0 of the package. (All deprecated names have reasonable replacements.) ### Changes - The two `OrderedDictionary.modifyValue` methods were renamed `updateValue`, to better align with the standard `updateValue` function (#90) ```swift /* Old: */ d.modifyValue(forKey: key, default: []) { $0.append(newValue) } /* New: */ d.updateValue(forKey: key, default: []) { $0.append(newValue) } /* Old: */ d.modifyValue(forKey: key, insertingDefault: [], at: 0) { $0.append(newValue) } /* New: */ d.updateValue(forKey: key, insertingDefault: [], at: 0) { $0.append(newValue) } ``` - `OrderedDictionary.subscript(offset:)` was removed; it used inconsistent terminology. To access a key-value pair at a given position, you can continue using the unlabeled subscript on the `elements` view. ```swift /* Deprecated: */ d[offset: 42] /* Replacement: */ d.element[42] ``` - The collections benchmarks were moved to a standalone nested package in a subdirectory of the repository, allowing the top-level package manifest to stop declaring a dependency on [swift-collections-benchmark](https://github.com/apple/swift-collections-benchmark). This will make it easier to add Swift Collections as a dependency, especially in projects such as the Package Manager (or the benchmarking tool itself). The old names for removed/renamed APIs are still available as deprecated members -- these will be removed in the 1.0 release. ### Pull requests - #81 Fix typos: missing subscript parameters (by @ejmarchant) - #82 Fix documentation for types conforming to ExpressibleByArrayLiteral or ExpressibleByDictionaryLiteral (by @ejmarchant) - #86 Stop depending on swift-collections-benchmark (by @lorentey) - #91 [OrderedDictionary] modifyValue → updateValue (by @lorentey) - #93 Add Benchmarks package to workspace (by @lorentey) - #92 [OrderedDictionary] Deprecate `subscript(offset:)` for now (by @lorentey) Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. This release consists of an update to the CMake config that is used during non-bootstrapped builds of the Swift toolchain. It contains no changes for package-based projects. ### Pull requests - #64: Add arm64 support to CMake build (by @neonichu) Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. ### Fixes - Work around a nondeterministic build issue that triggered a compiler crash on some machines (#56) - Basic support for building on OpenBSD (#52) - Building the package with COLLECTIONS_INTERNAL_CHECKS no longer fails (#53) ### Pull requests - #52: Changes to support OpenBSD (by @3405691582) - #53: Update invalid OrderedDictionary invariant check (by @vihanb) - #55: Fixing a small typo on quick help docs (by @rkreutz) - #54: Mark OrderedSetDiffingTests with availability (by @amonshiz) - #60: [CMake] Update config to prepare for SwiftPM adoption (by @lorentey) - #62: Work around another MergeModules crash (by @lorentey) - #63: [test] `checkCollection`: Don’t pass decreasing indices to `distance(from:to:)` (by @lorentey) Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. ### Fixes - The repository no longer contains files with invalid names on Windows (#33) - `Deque.append(contentsOf:)`, `.prepend(contentsOf:)` and the sequence-based initializer no longer crash when given an array instance bridged from Objective-C. (#27) - `OrderedSet.insert` is now marked `@discardableResult`. (#19) - The benchmark executable is no longer exposed as a public package product. (#28) ### Pull requests (You can also find a full list of issues resolved and PRs merged in this release by looking at the [0.0.3 milestone](https://github.com/apple/swift-collections/issues?q=milestone%3A0.0.3).) * #10: [meta] Update links in PR templates (by @lorentey) * #13: Add Package.resolved to .gitignore (by @maniramezan) * #21: Add the @discardableResult attribute to OrderedSet.insert(_:at:) (by @kielgillard) * #23: Fix CollectionTestCase calling super's setup on tearDown issue (by @abintom) * #25: Update to swift-collections-benchmark 0.0.2 (by @lorentey) * #26: [OrderedDictionary] Document encoding format (by @lorentey) * #28: [OrderedCollections] Correct spelling of BitsetTests filename (by @msteindorfer) * #32: Replace Index with Int where possible (by @Frizlab) * #34: Documentation: remove invalid file characters (by @compnerd) * #36: Remove the benchmark product from the package manifest (by @lorentey) * #40: Add Xcode template file with license comment. (by @vihanb) * #41: git: ignore vim swap files (by @compnerd) * #42: build: add a CMake based build system (by @compnerd) * #44: [Deque] Work around stdlib issue with Array.withContiguousStorageIfAvailable (by @lorentey) * #47: [manifest] Ignore CMake files (by @lorentey) * #48: [meta] Update dependencies (by @lorentey) * #49: [Deque][NFC] Remove unused code (by @lorentey) Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. ### Additions - `OrderedSet` now implements an efficient, linear time diffing algorithm, like Foundation's `NSOrderedSet` and SwiftUI's `List`. (https://github.com/apple/swift-collections/pull/6) ### Fixes - We've worked around a nondeterministic build issue that triggered a compiler crash on a minority of machines. (https://github.com/apple/swift-collections/issues/7) ### Pull requests (You can also find a full list of issues resolved and PRs merged in this release by looking at the [0.0.2 milestone](https://github.com/apple/swift-collections/issues?q=milestone%3A0.0.2).) * #6: Efficient diffing for OrderedSet (by @numist) * #8: Fixes link to combinatorics. (by @powerje) * #9: Minor doc fix (by @byaruhaf) * #12: Remove outdated passage in OrderedSet.init(minimumCapacity:persistent:) docs (by @lorentey) * #14: Correct typo for address sanitizer (by @toddpress) * #15: Update Package.resolved with swift-collections-benchmark package (by @Sajjon) * #16: Update Xcode schemes for the package (by @lorentey) * #18: Fix nondeterministic compiler crash in debug builds (by @lorentey) Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This release of SwiftSyntax is aligned with the release of Swift 5.8. Compared to 508.0.0, this release relaxes the version requirement for `swift-argument-parser`, resulting in fewer version conflicts for users of SwiftSyntax. This is the 508.0.0 release of SwiftSyntax, aligned with the release of Swift 5.8. To use this snapshot add the following dependency to your Package.swift: ```swift .package(url: "https://github.com/apple/swift-syntax", from: "508.0.0") ``` This is the 0.50700.1 release of SwiftSyntax that vends the parser library (`_InternalSwiftSyntaxParser.dylib`) as a binary framework dependency on macOS. To use this snapshot add the following dependency to your Package.swift: ```swift .package(url: "https://github.com/apple/swift-syntax", branch: "0.50700.1") ``` Or, if using a swift-tools-version ≤ 5.4: ```swift .package(url: "https://github.com/apple/swift-syntax", .branch("0.50700.1")) ``` ⚠️ Important: This release of SwiftSyntax is incompatible with the parser library included in the swift-5.7-RELEASE toolchain. On Linux, download a recent [swift-5.7-DEVELOPMENT-SNAPSHOT](https://www.swift.org/download/#swift-57-development) toolchain to use this SwiftSyntax version. On macOS, this version of SwiftSyntax is compatible with any recent Swift or Xcode toolchain because it includes the parser library as a binary dependency. This is the 0.50700.0 release of SwiftSyntax that vends the parser library (`_InternalSwiftSyntaxParser.dylib`) as a binary framework dependency on macOS. To use this snapshot add the following dependency to your Package.swift: ```swift .package(url: "https://github.com/apple/swift-syntax", branch: "0.50700.0") ``` Or, if using a swift-tools-version ≤ 5.4: ```swift .package(url: "https://github.com/apple/swift-syntax", .branch("0.50700.0")) ``` This is the 0.50600.1 release of SwiftSyntax that vends the parser library (`_InternalSwiftSyntaxParser.dylib`) as a binary framework dependency on macOS. To use this snapshot add the following dependency to your Package.swift: ```swift .package(url: "https://github.com/apple/swift-syntax", branch: "0.50600.1") ``` Or, if using a swift-tools-version ≤ 5.4: ```swift .package(url: "https://github.com/apple/swift-syntax", .branch("0.50600.1")) ``` This is the 0.50600.0 release of SwiftSyntax that vends the parser library (`_InternalSwiftSyntaxParser.dylib`) as a binary framework dependency on macOS. To use this snapshot add the following dependency to your Package.swift: ```swift .package(url: "https://github.com/apple/swift-syntax", branch: "0.50600.0") ``` Or, if using a swift-tools-version ≤ 5.4: ```swift .package(url: "https://github.com/apple/swift-syntax", .branch("0.50600.0")) ``` This is a development snapshot of the 0.50600.0 release of SwiftSyntax that vends the parser library (`_InternalSwiftSyntaxParser.dylib`) as a binary framework dependency on macOS. To use this snapshot add the following dependency to your `Package.swift`: ```swift .package(url: "https://github.com/apple/swift-syntax", branch: "0.50600.0-SNAPSHOT-2022-01-24") ``` Or, if using a swift-tools-version ≤ 5.4: ```swift .package(url: "https://github.com/apple/swift-syntax", .branch("0.50600.0-SNAPSHOT-2022-01-24")) ```

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This release is based on the Swift 5.8 release.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This release is compatible with Swift 5.8. Compared to 508.0.0, this release relaxes the version requirement for `swift-argument-parser`, resulting in fewer version conflicts for users of swift-format and SwiftSyntax. This release is compatible with Swift 5.8. Significant changes since the last release: * The `spacesAroundRangeFormationOperators` configuration option has been added to force a space around range formation operators like `...` and `..<`. * A new rule, `NoAssignmentInExpressions`, has been added that emits a linter finding if an assignment expression is found in another expression context (for example, `return x = y`). * Format and Lint plug-ins have been added that can be used from Swift Package Manager and Xcode. * Detection of "files that contain `XCTest`s" has been improved to include cases where `XCTest` is imported conditionally in a `#if` block. * Primary associated type clauses in `protocol` declarations are formatted correctly. * When a closure literal contains both a leading attribute and a capture list (e.g., `{ @MainActor [weak self] in ...`), a space is guaranteed between the attribute and capture list. * `Optional<T>` will not be automatically converted to the shorthand `T?` in positions where it would cause a performance issue due to subtle Swift initialization characteristics, like in member variable declarations. This is a development snapshot of the 0.50800.0 release of swift-format. This release is compatible with Swift 5.7. This update pins the swift-syntax dependency to at least 0.50700.1, which fixes an issue where new `if let` shorthand syntax was not recognized. This release is compatible with Swift 5.7. Significant changes since the last release: * The `AlwaysUseLowerCamelCase` rule no longer emits a warning for `override` declarations. (0e705f43b1b265c510b39b22d6eadcc1463f85a2) * The `UseWhereClausesInForLoops` rule won't hoist an `if` condition into a `where` clause if it also has an `else` block. (793d764d628bd16222f18e0678edbc28a93057b9) * `#if` postfix expressions now have improved formatting. (7216a18c7967fad06bae9211e0ee710fa9b788f7) * Files will not be overwritten if they are not changed during formatting, preserving their modification time and other metadata. (3b2b9b4349247927e2ae2d09169f6ad267977299) This release is compatible with Swift 5.6. This update fixes a build error caused by a conflicting Windows-only conformance from `swift-tools-support-core` and one that we added in our code base. (22f1843880ff57a3c288b7d76a204dec34397032) This release is compatible with Swift 5.6. Significant changes since the last release: * Diagnostics have been refactored as "findings". Users of swift-format as an API (via the `SwiftFormatter` and `SwiftLinter` classes) now receive warnings and errors via a new `Finding` type that is independent of `SwiftSyntax` diagnostic types, for greater flexibility. (7aa5df515fb910b95fbae67277dd782e1a641efc) * Diagnostics are now printed in color if standard error is connected to a terminal. This can be controlled with the `--color-diagnostics/--no-color-diagnostics` command line flags (to force color output when redirected to something other than a terminal, or to disable color output to a terminal). (4f90887ba823784e1d3b76cdd9779310843c5a57) * Formatting of `throws` and `async` property effects has been fixed. (f646a1f6803b7bd131553d1a348f3552d8c4f62e, 55fc4e23e16f463d650c45dc53c7abc731ca6de1) * The legacy `-m/--mode` flag has been removed. (defb00db9aa9b0564d487eba52a222c5267ba81a) This release is compatible with Swift 5.5. Significant changes since the last release: * New concurrency syntax added in Swift 5.5 is supported. (https://github.com/apple/swift-format/pull/258/commits/427d31451c36c2f7fb45dbd832c3b6f269bc1414) * Closures with attributes in their function signature are supported. (https://github.com/apple/swift-format/pull/258/commits/35e8687aff623042d188f6aaa24a1ecd27d55854) * Significant stability and performance improvements have been made to `--parallel` format mode. (https://github.com/apple/swift-format/pull/261/commits/6d500ea71337bc0581cc407b71fe09c106753fe8) * `generate-pipeline` no longer uses a hardcoded list of suppressed rules, instead marking those rules as opt-in. This makes two "new" rules available (they have always had implementations but have been suppressed): `UseEarlyExits` and `UseWhereClausesInForLoops`. These rules are not currently stable or well-tested so they are disabled by default. (https://github.com/apple/swift-format/pull/263/commits/6bd3a5512e3f686592c52f87ad6970f5a60e42b4) This release is compatible with Swift 5.4. Significant changes since the last release: * The `--parallel` flag supports formatting multiple files in parallel. This should be much faster when formatting large numbers of files. (a062ec84d3230f9b9055123c7bb2903780c84608) * The `--ignore-unparsable-files` flag is now honored in `lint` mode; unparsable files are silently ignored and no diagnostic is emitted. (fc3fab6bf6541e611830b122711af0bd750dec6f) * `#if` declarations surrounding `case` clauses inside a `switch` statement are formatted correctly. (8df2cb04f2aa41089cd14379552cb97bcc89133a) * `UseLetInEveryBoundCaseVariable` no longer produces incorrect diagnostics for certain patterns. (c3c17adbd93d9117f1d23fb05ffb7c435c23b581) * `BeginDocumentationCommentWithOneLineSummary` has been made opt-in by default. (22118db1668bb22af878d1ce31184533e419411b) * `UseSynthesizedInitializer` now produces more accurate diagnostics by considering the visibility of the stored properties in the type. (dd87cc2c9696ce8460265533471c75c225cde4fe) This release is compatible with Swift 5.3. Significant changes since the last release: * Support is added for rules to be opt-in rather than on-by-default. (40bab4e8b99d52dc561e62aa14e39d0d6cda7c17) * The following rules have been made opt-in, because they are either too strict for many real-world use cases or are not yet correct enough to enable universally. Existing configuration files will not be affected, but when using the default configuration, these rules will be off by default: (1c2a5a2d244b89ef10195799bbe9ca86ecc15bf3, 642c2d17e50936aa517f08c72eed9826bc163e4d) * `AllPublicDeclarationsHaveDocumentation` * `NeverForceUnwrap` * `NeverUseForceTry` * `NeverUseImplicitlyUnwrappedOptionals` * `NoLeadingUnderscores` * `ValidateDocumentationComments` * Improvements to `AlwaysUseLowerCamelCase`: * It is now applied to closure arguments and variables bound in `if/guard let` patterns. (7867cda76f800f6031cafa83793dd136f17b1c38) * Diagnostics are now clearer about the kind of declaration affected. (97628a8b0068fd0977ce50915c36f3dee8c5426a) * Functions that look like test case methods are excluded; for example, to support common naming schemes like `testSomeObject_inSomeState_actsSomeWay`. (90807621e2a52ca3432c56c3bb855bc89146b360) * Improvements to `ValidateDocumentationComments`: * A `Returns` section is no longer required for functions that return `Never`. (674b34df5114291df26f0f9edba8b94b76c28f80) * Presence of absence of the `Throws` section is now validated against the function signature. (57a5cb66a72bd04c9a07635b8a980573033dcc96) * Multiple trailing closures are formatted. (e286081a1342944236bde8653f5ca763ba61cfc3) * Fix a crash when linting a collection literal with single element and a trailing comma. (483580f1d3047272292aa516e06a02adc8b365aa) * Fixed invalid locations in some diagnostics. (ea02880b86bee22da9fbbfe37e43e17d75b673dd) * Keep `try` keyword next to the expression following it whenever possible, only breaking between them when necessary. (35fdb4fff0aeb9a506fccdfad98fab16d907c173) * Recursively apply `NoParensAroundCondition` to pick up nested occurrences. (ed45527f1c1891f90bb98c642275f43d164d56a1) * Do not remove semicolons between a `do` block and a `while` block. (cb4e6210c637b4ce3fd3ae81d0241c2c02895bfb) * Fix some situations where `OneVariableDeclarationPerLine` would incorrectly break declarations. (2b4364b7676964b430e66449e2981029e99ddd20) * Add a `indentSwitchCaseLabels` configuration option to control whether `case` statements inside a `switch` are indented. (2107603c7a0cb549a2e3fc7c35e5740dd4bee90e) * Speed and memory usage improvements when formatting and linting.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This release adds support for the CMake build in macOS on arm64. Thanks to @DanboDuan for the patch. This tag contains no code changes, but clarifies in the readme that API defined in a conformance to Differentiable cannot be source-stable, because Differentiable itself is not stable. Thanks @rxwei for reminding me to clarify this. Welcome to the first stable release of Swift Numerics! Not much has changed from 0.1.0, except that I'm declaring the API of RealModule and ComplexModule to be stable. There is some [expanded documentation](https://github.com/apple/swift-numerics/pull/193/files) for the `reciprocal` property on `AlgebraicField`, including discussion of error bounds for `Real` and `Complex` types. The only breaking change from 0.1.0 is that `Augmented.fastTwoSum` and `Augmented.twoProdFMA` have been [deprecated](https://github.com/apple/swift-numerics/pull/183/files) and [renamed](https://github.com/apple/swift-numerics/pull/181/files) `Augmented.sum(large:small:)` and `Augmented.product`. This change is not expected to effect many users, and the deprecation should make clear how to update your code if necessary. As always, raise a [GitHub issue](https://github.com/apple/swift-numerics/issues) or post on [the forums](https://forums.swift.org/c/related-projects/swift-numerics/56) if you have questions. Howdy buckaroos! It's been a while since the last release, as I've been busy with some real-life stuff. But now I'm back to the grindstone, and I've got a fun release for you. There's a bunch of cleanups and improvements from various contributors (@NevinBR and @markuswntr come to mind), but the big news is that [Complex types now conform to the ElementaryFunctions protocol](https://github.com/apple/swift-numerics/pull/162), which means that all your favorite math functions are available for complex types. The branch cuts of these complex functions should generally match C and C++'s (because all implementations follow Kahan's standard paper on the subject), though the exact numerical results will be slightly different in general. Unlike the real functions, the complex elementary functions are all implemented in Swift--we don't delegate to the host system math library. This is because the general quality of <complex.h> implementations is significantly lower than <math.h> implementations, and some platforms (Windows) don't provide those operations at all. In general, I believe that the basic algorithms used by Swift Numerics for these operations are as good as (and often better) than what C libraries provide, but there is always a possibility of bugs, especially with new code. Don't hesitate to raise an issue if you see anything you suspect. Special thanks to @compnerd for going above and beyond tracking down a [Swift bug](https://bugs.swift.org/browse/SR-13985) that held up this tag (and @eeckstein for fixing it!) This is a quick-fix release to address [a bug](https://github.com/apple/swift-numerics/issues/156) reported with Float16 availability in Xcode 12 on Catalina. No puns, sorry 😂 Hey all, lots of updates in this release: First, the big features: - Differentiable and Float16 support is live in Swift Numerics. These are protected behind swift version checks, so you'll only see them when you're building with a Swift 5.3 or later toolchain (because earlier toolchains don't have the necessary support). For Float16, you need to also be targeting a platform with support in the standard library (i.e. not macOS). For Differentiable, you need to be using a toolchain that was built with differentiable programming support enabled. - Approximate equality comparisons have been added for types conforming to Numeric when the associatedtype Magnitude conforms to FloatingPoint. This includes all of the Real types, but also includes Complex, and can be extended to lots of other useful types as well. The most basic use is: ``` a.isApproximatelyEqual(to: b) ``` which performs a comparison with default _relative_ tolerance. You can manually specify an absolute or relative tolerance (or both), as well as a norm to use via overloads and optional arguments. Consult the doc comments for more information now, but I plan to write a more in-depth README for the feature in the coming weeks. Two implementation details have also been added on `Real`, which are useful for building out other parts of the library: - `cosMinusOne(_ x: Self) -> Self` This is "just `expMinusOne(_:Self)`, but for cosine". It's a somewhat niche feature (and trivially implementable via the half-angle formula), but it turns out to be useful when building out ElementaryFunctions support for Complex types, so it seems to make good sense to make more broadly available. - `_mulAdd(_ a: Self, _ b: Self, _ c: Self) -> Self` This is intended to use _either_ an FMA or separate multiply and add to evaluate `a*b + c` as efficiently as possible. This is a much more niche implementation detail, and the name is subject to change (hence the underscore), but it's useful enough to expose for anyone who wants to use it. Speaking of ElementaryFunctions support for Complex types, that's something that's in progress now (https://github.com/apple/swift-numerics/pull/146). I'll be working through it over the next few weeks, and would love to have contributions. If you'd like to contribute, be sure to read the [_implementation goals_](https://github.com/apple/swift-numerics/pull/146/files#diff-09d59967445bcdd89e02e0534c77f51b). Simply borrowing from C or C++ implementations will probably not be sufficient for the goals we have and semantics defined for Complex, but you can use them as a starting point if you're willing to iterate with me a bit. Thanks everyone! Forums discussion here: https://forums.swift.org/t/0-0-7-release-notes/39680 There are a bunch of small changes in this release: - Added Windows support via CMake build system, contributed by @compnerd (special thanks for your patience!) - I removed the Complex benchmarks from the test targets. Semantically, benchmarks are not the same as tests, and we don't need these to run in the same conditions. Further, the Xcode benchmark infrastructure isn't quite what we want for these, and they don't work on Windows anyway, because clang does not support C complex multiplication or division on Windows. These benchmarks will return in the next release in the form of an executable target. - Complex&lt;T&gt; now conforms to Differentiable if you are using a toolchain that supports Differentiable programming and T is Differentiable. Thanks to @rxwei and @dan-zheng for their work on this. - Some documentation fixes for Complex fell out from work that @markuswntr has been doing on Quaternions (check out the Quaternions branch to play with it, and help review his PRs) - I fixed a bug in pow(Float/Double, Int) for exceptionally large exponents. It's unlikely that this ever caused any real problems, because it only occurs when the exponent is so large that the result should always be 0, 1, or infinity, but now we get the right answer for these cases. A reminder that Float16 support is available on the swift-5.3 branch, which will be merged to master when swift-5.3 is released. When that happens, I will also create a LTS swift-5.2 branch to support older toolchains that do not have Float16 support. Any questions or problems can be discussed on the GitHub repo or on the Swift Forums: https://forums.swift.org/t/0-0-6-release-notes/38146 There are two changes in this release: - [`AlgebraicField` now refines `SignedNumeric` instead of `Numeric`](https://github.com/apple/swift-numerics/pull/99). This should have no visible change for most users, because all conforming types (`Float`, `Double`, `Float80`, and `Complex`) already conform to `SignedNumeric`. However, users who have code that is generic over the `AlgebraicField` protocol can now use unary negation (or remove existing explicit `SignedNumeric` constraints from that code). - [The `Real` and `Complex` modules have been renamed `RealModule` and `ComplexModule`](https://github.com/apple/swift-numerics/pull/97). If you import `Numerics`, then this change does not affect you. However, if you currently import either `Real` or `Complex` directly, you will need to update your import statements. (sorry!) This is not a change that I make lightly; I would very much prefer to avoid this sort of churn, even though Swift Numerics hasn't yet declared 1.0. However, there are real limitations of the current name lookup system, which prevents use of some nice patterns when a module name shadows a type. E.g. with this change, a user who mostly only wants to work with complex doubles can do the following: ```swift import ComplexModule typealias Complex = ComplexModule.Complex<Double> // Can now use the simpler name Complex for Complex<Double>: func foo(_ z: Complex) -> Complex { ... } // But can still get at the generic type when necessary: let a = ComplexModule.Complex<Float> ``` Any Swift Numerics module that might have this ambiguity will be suffixed with `Module` in the future (just like the pattern of protocols being suffixed with `Protocol` when necessary to break ambiguity). As always, if you have any questions or comments, there is a [forums thread for discussing this release](https://forums.swift.org/t/0-0-5-release-notes/33991). There are two changes in this release to call out specifically: - Complex's conformance to Codable now uses an *unkeyed* container, so e.g. `.zero` gets encoded as `[0,0]` in JSON instead of the old `{"x":0, "y":0}`. - There's a new protocol, `AlgebraicField` refining `Numeric` by adding the `/`, `/=` operators, and a `.reciprocal: Self?` property. The `Real` protocol refines it and `Complex<T>` conforms to it, allowing you to write code that is generic over them. There are some additional operations that it probably makes sense to add to this protocol (e.g. square root); I expect to add them gradually as needed. I also want to draw special attention to [a change](https://github.com/apple/swift-numerics/issues/94) that I expect to make in the *next* tag. In order to make certain use patterns simpler, I intend to give the `Complex` module a name that doesn't conflict with the `Complex` type. If you have opinions about this change, or suggestions for a naming pattern to adopt for modules in Swift Numerics, please weigh in on that thread. If you have any questions, use this [discussion thread](https://forums.swift.org/t/0-0-4-release-notes/32860) on the Swift forums. In earlier releases, `Real.pow(Self, Int)` simply called through to `libm_pow`. This is generally acceptable on platforms with a decent math library, but gets some cases wrong for `Float` and `Double` when the exponent is so large that it would be rounded in conversion to `Self`. For example, consider `Float.pow(-1, 0x1000001)`. Since the exponent is odd, the result should be `-1`, but when we simply called `libm_pow(-1, Float(0x1000001))`, the exponent was rounded to an even number, and the result was `1`. This behavior is fixed in this release; in particular the parity of integer exponents is always preserved, so that we will not have sign errors like above. There is still additional work to be done on the `Real.pow` implementations--especially to provide better support for platforms with suspect math libraries--but this is a significant improvement to these operations.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Minor - ChaCha20 CTR Encryption (#169, patch credit to @btoms20) ### SemVer Patch - Drop support for Swift 5.5 (#172) ### Other Changes - Set CRYPTO_IN_SWIFTPM (#177, patch credit to @etcwilde) ### SemVer Patch - Update BoringSSL to abfd5ebc87ddca0fab9fca067c9d7edbc355eae8 (#171) ### Other Changes - Fix broken link (#153, patch credit to @Sajjon) - Update Wycheproof 'x25519_test.json' to v1 (#155, patch credit to @Sajjon) - Update Wycheproof aes_gcm.json to v1 (#156, patch credit to @Sajjon) - Update Wycheproof chacha20_poly1305 to v1 (#157, patch credit to @Sajjon) - Update Wycheproof ecdh_secp256r1_ecpoint_test.json to v1 (#158, patch credit to @Sajjon) - Update Wycheproof eddsa_test to v1 (renamed to ed25519_test) (#159, patch credit to @Sajjon) - Update Wycheproof ecdh_secp256r1_test.json to v1 (#160, patch credit to @Sajjon) - Update Wycheproof ecdh_secp384r1_ecpoint_test.json to v1 (#161, patch credit to @Sajjon) - Update Wycheproof ecdh_secp384r1_test.json to v1 (#162, patch credit to @Sajjon) - Update Wycheproof ecdh_secp521r1_test.json to v1 (#163, patch credit to @Sajjon) - Update Wycheproof ecdh_secp521r1_ecpoint_test.json to v1 (#164, patch credit to @Sajjon) - Update Wycheproof multiple ECDSA test vectors to v1 (#166, patch credit to @Sajjon) - Add five new Wycheproof ECDSA test vectors using IEEE P1363 format (#167, patch credit to @Sajjon) - Exclude AES from CMake (#152) - Add docker-compose file for Swift 5.8 and 5.9 (#170) ### SemVer Minor - Make RSA public key formats consistent on all platforms (#151) ### SemVer Minor - Support SwiftWasm (#145, patch credit to @AndrewBarba) ### Other Changes - build: add `ARM64` spelling for Windows (#148, patch credit to @compnerd) - Set up CMake build for _CryptoExtras (#144) ### SemVer Patch - Add AES block function to CryptoExtras (#142) - Update BoringSSL to 45b8d7bbd771cbf7e116db2ba1f1cc7af959497e (#143) This release contains no semantic changes, only adjustments to the CMake build. ### Other Changes - build: adjust linking for Crypto (#137, patch credit to @compnerd) This release contains no functional changes ### Other Changes - Link Foundation in CryptoBoringWrapper (#136) ### SemVer Patch - Add Linux support for PKCS#1 RSA public keys (#135) ### SemVer Minor - Update Swift Crypto for the Ventura API (#123) - Raise minimum supported Swift version from 5.4 to 5.5 (#131) ### SemVer Patch - truncating for big `contentLength` (#119, patch credit to @d-date) - Fix ASN.1 serialization when content greater than or equal to 128 bytes (#120, patch credit to @swiftty) - Crypto: explicitly type the array slice (#122, patch credit to @compnerd) - Make BoringSSL wrapper match CryptoKit behaviour when working with x9.63 (#128) - Provide AES-GCM-SIV in CryptoExtras (#133) - Update BoringSSL to 0faffc7a30eeb195248ea43056f4848e2a9b1c6d (#121, #132, #134) ### Other Changes - Update Python script to Python 3 (#117, patch credit to @0xTim) - build: use cctols ranlib on Darwin (#129, patch credit to @edymtt) - Use 5.7 nightlies (#118) - Validate missing imports in CI (#127) ### SemVer Minor - Drop support for Swift 5.2 and 5.3 (#111) ### SemVer Patch - Avoid unnecessary copies of BoringSSL (#94) - Update BoringSSL to f961de5c47ed265c3e758ec70dd15ece20809962 (#115) ### Other Changes - Use SPM API diff checker (#112)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This is a bug fix release restoring the ability to build this package on Windows. ## What's Changed * Revert "FileOperations: Add Windows implementation for FileDescriptor.resize(to:)" in https://github.com/apple/swift-system/pull/93 **Full Changelog**: https://github.com/apple/swift-system/compare/1.2.0...1.2.1 ## What's New * FileDescriptor: Add resize(to newSize:) by @simonjbeaumont in https://github.com/apple/swift-system/pull/82 ## What's Changed * Unify availability annotations & introduce a script to manage them by @lorentey in https://github.com/apple/swift-system/pull/75 * Update Linux tests manifest by @dduan in https://github.com/apple/swift-system/pull/81 * docs: Removed duplicate paragraph from FileDescriptor.writeAll(_:) docs by @simonjbeaumont in https://github.com/apple/swift-system/pull/85 * Unbreak the Windows port by @lorentey in https://github.com/apple/swift-system/pull/88 * Rebind byte types safely by @glessard in https://github.com/apple/swift-system/pull/79 * Fix broken links. by @amartini51 in https://github.com/apple/swift-system/pull/77 * Mitigate misuse of Swift's pointer conversion feature by @glessard in https://github.com/apple/swift-system/pull/80 * Import C module as `@_implementationOnly` by @colemancda in https://github.com/apple/swift-system/pull/83 * FileOperations: Add Windows implementation for FileDescriptor.resize(to:) by @simonjbeaumont in https://github.com/apple/swift-system/pull/89 ## New Contributors * @dduan made their first contribution in https://github.com/apple/swift-system/pull/81 * @simonjbeaumont made their first contribution in https://github.com/apple/swift-system/pull/85 * @glessard made their first contribution in https://github.com/apple/swift-system/pull/79 * @colemancda made their first contribution in https://github.com/apple/swift-system/pull/83 **Full Changelog**: https://github.com/apple/swift-system/compare/1.1.1...1.2.0 ## What's Changed * build: install CSystem into the system by @compnerd in https://github.com/apple/swift-system/pull/74 **Full Changelog**: https://github.com/apple/swift-system/compare/1.1.0...1.1.1 Picks up pipe API and cmake changes. ## What's Changed * Implement `FileDescriptor.Pipe()` by @GeorgeLyon in https://github.com/apple/swift-system/pull/58 * Minor fixes in documentation comments by @amartini51 in https://github.com/apple/swift-system/pull/69 * update cmake setup so that the library can be used by SwiftPM cmake build by @tomerd in https://github.com/apple/swift-system/pull/73 ## New Contributors * @GeorgeLyon made their first contribution in https://github.com/apple/swift-system/pull/58 * @tomerd made their first contribution in https://github.com/apple/swift-system/pull/73 **Full Changelog**: https://github.com/apple/swift-system/compare/1.0.0...1.0.1 Official 1.0 release! System is already source and binary stable (at least on Darwin), so in practice this doesn't change much about System's development or guarantees (`1.0.0` is effectively the same as `0.0.3`). But, it does formalize the source stability guarantee for clients of the package. Contains bug fixes for Windows, and minor fixes for SystemChar. * [FilePath Syntactic Operations](https://github.com/apple/swift-system/pull/14) * decompose a path, analyze a path, components view, mutate a path, etc * [Standard file descriptors](https://github.com/apple/swift-system/pull/21) * static `FileDescriptor.standardInput`, `FileDescriptor.standardOutput`, `FileDescriptor.standardError` * [dup/dup2](https://github.com/apple/swift-system/pull/28) * `FileDescriptor.duplicate`, with optional `as` target. Initial release

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Matches the Swift 5.1 release.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This minor release improves support for recent Swift releases, adds new functionality and resolves some known issues. ### Changes - This release requires Swift 5.6 or better. (Clients on older toolchains will automatically remain on the 1.0 releases.) (#67) - `AtomicReference` is now unconditionally available on all supported platforms. (#65 by @kelvin13) - `ManagedAtomic` now conforms to `Sendable` when its `Value` is `Sendable`. (#45) - `RawRepresentable` types can now opt into support for atomic operations on their optional values as long as their underlying `RawValue` also supports it. (#42 by @glessard) ```swift struct SomeValue: RawRepresentable, AtomicOptionalWrappable { var rawValue: UnsafeRawPointer init(rawValue: UnsafeRawPointer) { self.rawValue = rawValue } } let atomic: ManagedAtomic<SomeValue> // OK let atomic2: ManagedAtomic<SomeValue?> // Also OK! ``` - The `weakCompareExchange` operation now comes with a variant that takes a single ordering (#75). This makes it less verbose to use it in the common case where the same ordering is needed on both the success and the failure paths. ```swift let atomic = ManagedAtomic<Int>(42) var original = 0 var exchanged = false repeat { (exchanged, original) = atomic.weakCompareExchange( expected: original, desired: 23, ordering: .relaxed) // no need to specify a separate failureOrdering! } while !exchanged ``` - `DoubleWord.low` and `DoubleWord.high` are now deprecated (#70). Use `first` and `second` instead. - This release lays the groundwork for replacing the use of C atomics with native Swift compiler intrinsics (#74). When it eventually becomes stable, this change will allow swift-atomics to support Windows (#56), and it will resolve a multitude of build problems on other platforms (e.g., #54, #55, #62, #8). Version 1.1 ships with experimental support for building the package in this mode; however, this mode is not enabled by default, and it is subject to arbitrarily change in any future release. ### Fixes - `ManagedAtomicLazyReference` no longer leaks its value when it is deinitialized (#66). - `AtomicReference` conformances on non-final classes no longer emit a compiler warning in Swift 5.7 and later (#53). Atomic references now fully support class hierarchies, but only the superclass that introduced the `AtomicReference` conformance can be used as the type argument to `ManagedAtomic` or `UnsafeAtomic`. This turns a previously undiagnosed type safety violation into an unconditional compile-time error: ```swift class Base: AtomicReference {} // 1.0: warning: Non-final class 'Base' cannot safely conform to protocol // 'AtomicValue', which requires that 'Self.AtomicRepresentation.Value' // is exactly equal to 'Self'; this is an error in Swift 6 // 1.1: OK class Derived: Base {} let ref1: ManagedAtomic<Base> = .init(Derived()) // OK let ref2: ManagedAtomic<Derived> = .init(Derived()) // 1.0: // no error, silent type safety violation // 1.1+: // error: 'ManagedAtomic' requires the types 'Derived' // and 'Base' be equivalent ``` - All atomic operations are now implemented in terms of `Int8`, `Int16`, `Int32`, `Int64`, `Int`, or `DoubleWord`. The package no longer uses non-standard C to implement atomic operations on `Bool` (#37). - Building the package tests is now far less resource-intensive, considerably speeding up builds on some memory-constrained systems (#71). ### Pull Requests - #42 Implement AtomicStorage for Optionals of RawRepresentable types (by @glessard) - #58 Fix support for non-final classes in AtomicReference (by @lorentey) - #65 enable AtomicReference everywhere (by @kelvin13) - #67 Bump minimum required toolchain to Swift 5.6 (by @lorentey) - #68 Remove obsolete workarounds for older toolchains (by @lorentey) - #69 ManagedAtomicLazyReference: Properly dispose object on deinit (by @lorentey) - #70 Simplify shims (by @lorentey) - #71 Resolve some test issues (by @lorentey) - #72 [test] Fix basic tests to to actually cover weakCompareExchange (by @lorentey) - #73 Update AtomicOptionalWrappable support for RawRepresentable types (by @lorentey) - #74 Add support for using LLVM intrinsics instead of C atomics (by @lorentey) - #76 Add a weakCompareExchange variant that only takes a single ordering (by @lorentey) - #77 Add an Xcode project exercising native builtins in a monomodule configuration (by @lorentey) - #78 Fix compatibility with Swift 5.6 (by @lorentey) - #80 Update file headers (by @lorentey) - #81 Fix some edge cases under 5.6 (by @lorentey) - #82 1.1 release preparations (by @lorentey) - #83 Utilities/run-full-tests.sh: Use a different derived data path when building the Xcode project (by @lorentey) **Full diffs**: https://github.com/apple/swift-atomics/compare/1.0.3...1.1.0 Thank you very much to everyone who contributed to this release! This is a documentation update, including the addition of basic DocC documentation bundles. The only other change is a fix to the CMake build configuration. ## Changes The package now contains documentation bundles, enabling nicer presentation of API documentation in DocC. ## Pull Requests * Update README for autogenerated subdirectories by @chornge in https://github.com/apple/swift-atomics/pull/49 * [Documentation] Add a note that TSan does not support fences. by @karwa in https://github.com/apple/swift-atomics/pull/50 * fix cmake build when Atomics is built as dependency by @michaelknoch in https://github.com/apple/swift-atomics/pull/52 ## New Contributors * @chornge made their first contribution in https://github.com/apple/swift-atomics/pull/49 * @karwa made their first contribution in https://github.com/apple/swift-atomics/pull/50 * @michaelknoch made their first contribution in https://github.com/apple/swift-atomics/pull/52 **Full Changelog**: https://github.com/apple/swift-atomics/compare/1.0.2...1.0.3 This is a patch release that introduces initial support for building this package with the Swift 5.5 compiler. (More fully-featured support with additional `Sendable` conformances will come in a future minor release.) #### Fixes - The package now has a workaround for an arm64 code generation issue for double wide atomics in the version of LLVM that ships in Swift 5.5. (#41) - When building with Swift 5.5, `UnsafeAtomic` and `UnsafeAtomicLazyReference` now only conform to `Sendable` when their value is. Swift 5.5 implicitly adds unconditional conformances to these types in 1.0.1, which isn't right. (#47) - The package now has better support for building with CMake. (#39) (Note that the CMake build configuration is intended only to enable the use of this package within Swift toolchain builds. It isn't part of the package's public API, so it is subject to change in any release.) ### Pull Requests - #38 [shims] Only define atomic shims in Swift's Clang Importer (by @lorentey) - #39 [cmake] Fix building with CMake (by @lorentey) - #40 Add support test script (by @lorentey) - #43 Implement double-wide loads with compare-exchange on arm64 in debug builds with the Swift 5.5 compiler (by @lorentey) - #44 Update utility scripts (by @lorentey) - #48 Fix `UnsafeAtomic`'s `Sendable` conformance (by @lorentey) Thank you to everyone who contributed to this release! This is a patch release containing several bug fixes. #### Fixes - The package now builds successfully on 32-bit architectures (i386, armv7) (#33) - The package manifest was adjusted to prevent SwiftPM warnings about unknown files in source directories. - Several types are now `@frozen` to match their `@inlinable` initializers. (This package isn't ABI stable, so this change is a no-op in all supported configurations.) ### Pull Requests - #34 [shims] Fix i386/armv7 regression introduced in #26 (by @lorentey) - #35 [manifest] Fix warnings in 5.3 toolchains (by @lorentey) - #36 Fix build errors with library evolution enabled (by @lorentey) Thank you to everyone who contributed to this release! This release marks an important milestone for this package -- the advent of source stability! #### Changes - The public API of Swift Atomics is now considered source stable. The README defines what we consider public API. - Swift Atomics now requires a Swift 5.3 or later toolchain. - The low-level (pointer-based) atomic boolean operations are now public. (They were accidentally omitted from previous releases.) - The package now includes a CMake-based build method for bootstrapping purposes. This isn't considered stable; it may be removed or arbitrarily changed in any new release, including patch releases. #### Pull requests - #20 DoubleWord._readersBitWidth: Switch to using Int.bitWidth (by @lorentey) - #24 Mark the additional Bool methods as public (by @dfunckt) - #25 build: add a CMake based build for Atomics (by @compnerd) - #26 _AtomicShims: simplify double word setup (by @compnerd) - #28 gitignore: ignore vim swap files (by @compnerd) - #29 Tests: add XCTest manifest for non-SPM based builds (by @compnerd) - #30 Bump required toolchain version to 5.3 (by @lorentey) - #31 Declare Atomics source stable and describe what we consider public API (by @lorentey) - #32 [NFC] Update copyright notices (by @lorentey) Thank you to everyone who contributed to this release! ### Fixes - Adds basic support for building with the Swift 5.2 toolchains. - Resolves a warning about the `arm64_32` architecture emitted by swift.org compiler builds. ## Changes - On Linux only, support for double-wide atomics is unavailable by default on x86_64 CPUs. To enable double-wide atomic functionality, you have to manually switch on support for the `cmpxchg16b` instruction: ``` $ swift build -Xcc -mcx16 -Xswiftc -DENABLE_DOUBLEWIDE_ATOMICS -c release ``` Code containing `cmpxchg16b` will run on all but the earliest AMD x86_64 CPUs. (You can verify your target CPU supports it by checking that the `cx16` flag is present in /proc/cpuinfo.) - The Swift Atomics test suite now requires `--enable-test-discovery` on non-Apple platforms. Initial release.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ## What's Changed * Update CI by @yim-lee in https://github.com/apple/swift-metrics/pull/124 * Use UUID instead of NSUUID in MetricsTests by @fabianfett in https://github.com/apple/swift-metrics/pull/126 * Add Package.resolved to .gitignore by @fabianfett in https://github.com/apple/swift-metrics/pull/125 * add "meter" - a new type of metric and metric handler by @tomerd in https://github.com/apple/swift-metrics/pull/123 * Use the MetricsTestKit in the MetricsTests rather than using a copy of the TestMetrics utilities by @hamzahrmalik in https://github.com/apple/swift-metrics/pull/128 * MetricsTestKit: expose all metrics publicly. This allows users to run checks on counters when they might not know the exact label by @hamzahrmalik in https://github.com/apple/swift-metrics/pull/127 * Make 'values' on TestCounter, TestRecorder and TestMeter public by @hamzahrmalik in https://github.com/apple/swift-metrics/pull/129 ## New Contributors * @hamzahrmalik made their first contribution in https://github.com/apple/swift-metrics/pull/128 **Full Changelog**: https://github.com/apple/swift-metrics/compare/2.3.4...2.4.0 ## What's Changed * Propagate displayUnit when using MultiplexMetricsHandler by @gjcairo in https://github.com/apple/swift-metrics/pull/122 ### CI updates * Add CI for Swift 5.8 and update nightly to Ubuntu 22.04 by @yim-lee in https://github.com/apple/swift-metrics/pull/121 ## New Contributors * @gjcairo made their first contribution in https://github.com/apple/swift-metrics/pull/122 - thank you! **Full Changelog**: https://github.com/apple/swift-metrics/compare/2.3.3...2.3.4 ## What's Changed * Make `MetricsFactory` Sendable by @fabianfett in https://github.com/apple/swift-metrics/pull/116 * +docc prepare for docc publishing by @ktoso in https://github.com/apple/swift-metrics/pull/118 * Add .spi.yml for Swift Package Index DocC support by @yim-lee in https://github.com/apple/swift-metrics/pull/119 **Full Changelog**: https://github.com/apple/swift-metrics/compare/2.3.2...2.3.3 ## What's Changed * better abstration for MetricsSystem state by @tomerd in https://github.com/apple/swift-metrics/pull/112 * adopt sendable by @tomerd in https://github.com/apple/swift-metrics/pull/109 * Remove testable import from TestMetrics. by @fabianfett in https://github.com/apple/swift-metrics/pull/113 **Full Changelog**: https://github.com/apple/swift-metrics/compare/2.3.1...2.3.2 ## What's Changed * Expose `MetricsTestKit` as a product by @fabianfett in https://github.com/apple/swift-metrics/pull/111 ## New Contributors * @fabianfett made their first contribution in https://github.com/apple/swift-metrics/pull/111 **Full Changelog**: https://github.com/apple/swift-metrics/compare/2.3.0...2.3.1 - https://github.com/apple/swift-metrics/pull/106 Introduced new `MetricsTestKit` module that allows asserting certain metrics have been emitted etc. - we will provide more documentation soon; meanwhile you can use this test as reference for how to use the testkit here's how one uses it for those curious https://github.com/apple/swift-cluster-membership/blob/main/Tests/SWIMTests/SWIMMetricsTests.swift New addition allowing for floating point counters. This API will be right away supported by SwiftPrometheus, other libs may follow. ## SemVer Minor ### New API: - Add `FloatingPointCounter` which allows reporting floating point metrics when necessary. Thanks @rauhul! A minor new API to enable SystemMetrics from the new swift-metrics-extras (coming soon) repository. # SemVer Minor New API: - Expose `MetricsSystem.withWriterLock`so it can be invoked by alternate "bootstrap" functions, such as SystemMetrics; https://github.com/apple/swift-metrics/pull/86 Thanks @MrLotU ! --- For details on the changes please refer to the [0.2.1 milestone](https://github.com/apple/swift-metrics/milestone/14?closed=1) # SemVer Minor New API: - `Timer.recordInterval(since:)` for easier reporting of time since a "start" `DispatchTime` https://github.com/apple/swift-metrics/pull/83 - thank you @slashmo! # SemVer Patch - Metrics now include their labels when printed to ease debugging https://github.com/apple/swift-metrics/pull/82 --- For details on the changes please refer to the [0.2.1 milestone](https://github.com/apple/swift-metrics/milestone/11?closed=1) # SemVer Major * Add microseconds to the TimeUnit enum #64 Important note: The 1.x (previous) version of swift-metrics included a `TimeUnit` enum which was missing a `microseconds` case. Since adding a case to an enum is an API breaking change, we needed to release this change as sever 2.0.0. We also used this opportunity to change the enum to a struct so we can add more time unit without breaking the API. That said, since 1.x and 2.x are almost API compatible, `TimeUnit` is not used by swift-metrics directly and only used by few libraries that depend on it, most libraries should use the following dependency to avoid a fragmentation of ecosystem: ``` .package(url: "https://github.com/apple/swift-metrics.git", "1.0.0" ..< "3.0.0") ```

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ## Highlights This release fixes a number of bugs preventing stable usage of the beta.2 release in a long running cluster (https://github.com/apple/swift-distributed-actors/pull/1059). It also performs a number of destructive renames while we still have the ability to do so. - **Module rename (!)** The `DistributedActors` module has been renamed to `DistributedCluster` as it explains more precisely what this module is offering (the `ClusterSystem`) type. - The `Node` and `UniqueNode` types have been changed to `Cluster.Endpoint` and `Cluster.Node` respectively. See https://github.com/apple/swift-distributed-actors/pull/1077 for a more detailed explanation. Internally we also adopted a new integration testing framework - offering MultiNode tests. This multi node testing framework will initially be matured internally before making it available to users outside the package. https://github.com/apple/swift-distributed-actors/pull/1055 ## What's Changed * Convert SWIMActorShell to distributed actor by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/977 * =reception immediately flush already known regs to a listing by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1049 * =reception prevent receptionist strong retaining actors by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1050 * Rewrite SWIMActor.sendPingRequests to use Swift concurrency by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1052 * New multi-node infrastructure for integration tests by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1055 * =receptionist Fix receptionist crash on concurrent registrations; those are fine and expected by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1059 * Correct typos in documentation by @PeterAdams-A in https://github.com/apple/swift-distributed-actors/pull/1065 * =build workaround for SwiftPM not allowing people to consume current `main` by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1067 * Fix typo: Lifecycle example by @MaximBazarov in https://github.com/apple/swift-distributed-actors/pull/1069 * =build fix how we declare the multi-node plugin by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1068 * =doc explain waiting for joined nodes better, fix link #1070 by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1072 * Rename DistributedActors -> DistributedCluster module by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1071 * Fix overflow in TimeSpec addition on 32-bit architectures by @orobio in https://github.com/apple/swift-distributed-actors/pull/1074 * !all node renames: node -> endpoint; unique node -> node by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1077 * -test remove known flaky test of unsupported feature by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1079 ## New Contributors * @PeterAdams-A made their first contribution in https://github.com/apple/swift-distributed-actors/pull/1065 * @MaximBazarov made their first contribution in https://github.com/apple/swift-distributed-actors/pull/1069 * @orobio made their first contribution in https://github.com/apple/swift-distributed-actors/pull/1074 **Full Changelog**: https://github.com/apple/swift-distributed-actors/compare/1.0.0-beta.2...1.0.0-beta.3 This release is primarily aimed at supporting Swift 5.7 - due to the updated Swift syntax dependency. ## What's Changed * Add Swift 5.7 support to legacy release/0.x branch. by @mrstegeman in https://github.com/apple/swift-distributed-actors/pull/1062 **Full Changelog**: https://github.com/apple/swift-distributed-actors/compare/0.7.0...0.7.1 This beta release marks major improvements in all surface APIs and completes most of the public surface move to distributed actors and async await. We also added more documentation and will continue adding more examples and guides about using and deploying distributed actor clusters. A few API changes may still happen like making more methods async etc. ## Documentation Latest beta documentation is hosted on [github pages](https://apple.github.io/swift-distributed-actors/1.0.0-beta.2/documentation/distributedactors). ## Milestone The [1.0.0-beta.2](https://github.com/apple/swift-distributed-actors/milestone/32?closed=1) milestone contains all closed issues for your reference. ## What's Changed * Make sure to cancel listing when task is cancelled by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/966 * Receptionist should flush registrations in order by version by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/967 * Update receptionist tests by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/968 * Make ClusterControl.membershipSnapshot async property by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/969 * Add API to 'await joining cluster' by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/972 * Safer lifecycle watch api by @ktoso in https://github.com/apple/swift-distributed-actors/pull/961 * =docker Fix 5.7 docker image name by @ktoso in https://github.com/apple/swift-distributed-actors/pull/974 * Codable improvements for ActorID tags by @ktoso in https://github.com/apple/swift-distributed-actors/pull/915 * !context store lifecycle in DistributedActorContext; internal only by @ktoso in https://github.com/apple/swift-distributed-actors/pull/976 * fix wrong cross module usage; seems this was not caught by CI / SwiftPM by @ktoso in https://github.com/apple/swift-distributed-actors/pull/981 * Use #filePath instead of #file by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/984 * update swift tools version and required apple platforms by @JaapWijnen in https://github.com/apple/swift-distributed-actors/pull/982 * Fix #filePath related warnings by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/985 * Use AsyncTimerSequence from swift-async-algorithms by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/986 * Implement setting actor metadata with property wrapper fields by @ktoso in https://github.com/apple/swift-distributed-actors/pull/988 * Dead letter when remote call target is dead by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/989 * Add ability to watch distributed actor with TestProbe by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/991 * Silence OpLogDistributedReceptionist.sendAckOps timeout logs by @PopFlamingo in https://github.com/apple/swift-distributed-actors/pull/996 * Use correct error type for timeout error silencing by @PopFlamingo in https://github.com/apple/swift-distributed-actors/pull/997 * Remove all instances of AskResponse.wait() use by @ruslanskorb in https://github.com/apple/swift-distributed-actors/pull/998 * Fix logging level setting issue by @PopFlamingo in https://github.com/apple/swift-distributed-actors/pull/1003 * Implement ActorSingleton for DistributedActor by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/980 * Support seed nodes by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1005 * Remove unused LamportClock type by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1007 * Skip flaky test: ClusterLeaderActionsClusteredTests.test_singleLeader by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1008 * Make installSwiftBacktrace public before we remove it by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1006 * Implement generic distributed actor method call by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1013 * Change generic EventStream<Event> to ClusterEventStream and convert to actor by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1012 * Address remaining feedback in #1012 by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1015 * Distributed Actor support in Cluster Singleton by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1010 * Add .devcontainer by @PopFlamingo in https://github.com/apple/swift-distributed-actors/pull/995 * Hide VersionVector by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1023 * Avoid errors in old toolchains, add to-be-removed convenience keyword by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1026 * Make remote call errors configurable by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1020 * Make public enums into structs or hide them (part 1) by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1025 * Final polish and docs for singleton by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1022 * Improve old betas compatibility by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1029 * Make public enums into structs or hide them (part 2) by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1028 * -build remove toy "exec app" app by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1033 * =receptionist lookup() trying to cast stub actor by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1032 * Make public enums into structs or hide them (part 3 - final) by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/1037 * -jazzy remove jazzy; we're only using docc now by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1038 * [docc] Fail soundness on docc warnings (bad links), fix a few warnings by @ktoso in https://github.com/apple/swift-distributed-actors/pull/1027 ## New Contributors * @JaapWijnen made their first contribution in https://github.com/apple/swift-distributed-actors/pull/982 * @ruslanskorb made their first contribution in https://github.com/apple/swift-distributed-actors/pull/998 Thank you to all contributors! **Full Changelog**: https://github.com/apple/swift-distributed-actors/compare/1.0.0-beta.1.1...1.0.0-beta.2 ## Require macOS 13 / iOS 16 With macOS 13 beta announced, we're able to express the minimum deployment targets in Package.swift and allow developers to use this library without the `-disable-availability-checking` flags. Use macOS 13 Ventura and Xcode 14.0 beta to build this project, and develop using distributed actors 🎉 ## What's Changed * Implement remoteCall without ask actors by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/956 * More API and documentation cleanups by @ktoso in https://github.com/apple/swift-distributed-actors/pull/954 * Deprecations by @ktoso in https://github.com/apple/swift-distributed-actors/pull/960 * Use Swift's time types by @yim-lee in https://github.com/apple/swift-distributed-actors/pull/962 * Remove unused LamportClock type by @ktoso in https://github.com/apple/swift-distributed-actors/pull/963 * Remove -disable-availability-checking, Swift 5.7 is part of Xcode 14.0 and has right availabilities now by @ktoso in https://github.com/apple/swift-distributed-actors/pull/964 **Full Changelog**: https://github.com/apple/swift-distributed-actors/compare/1.0.0-beta.1...1.0.0-beta.1.1 ### First Beta This is the first beta release of the distributed actors and cluster library. ### Supported features - a `ClusterSystem` implementation, enabling clustered `distributed actor` instances, - cluster events `system.cluster.events`, i.e. nodes joining, becoming down and leaving, - observe actor lifecycle and termination with `LifecycleWatch`, - a cluster-wide `DistributedReceptionist` implementation enabling actor discovery, - and more! Refer to the [reference documentation]() for more details Support Swift and Swift Syntax 5.6 The upcoming Swift 5.7 release will not be supported on the release/0.x branch and we will move on towards the language provided distributed actor features. ## What's Changed * Add Swift 5.6 support. by @mrstegeman in https://github.com/apple/swift-distributed-actors/pull/870 * 0.x CI setup by @tomerd in https://github.com/apple/swift-distributed-actors/pull/871 * Adapt codebase for Swift 5.6 release version by @segabor in https://github.com/apple/swift-distributed-actors/pull/876 ## New Contributors * @mrstegeman made their first contribution in https://github.com/apple/swift-distributed-actors/pull/870 * @segabor made their first contribution in https://github.com/apple/swift-distributed-actors/pull/876 **Full Changelog**: https://github.com/apple/swift-distributed-actors/compare/0.6.10...0.7.0 ## What's Changed * Down replaced cluster members by @budde in https://github.com/apple/swift-distributed-actors/pull/867 **Full Changelog**: https://github.com/apple/swift-distributed-actors/compare/0.6.9...0.6.10 #### Minor - adjust for Swift 5.5 ### Patch - Fix building in release mode in Swift 5.4 - Update some code that was causing warnings / errors - Fix and add debugging fir metrics which may crash with underflow https://github.com/apple/swift-distributed-actors/issues/802 Thanks @budde - Fix 5.4 builds - update service discovery to 1.0 More details: https://github.com/apple/swift-distributed-actors/milestone/22?closed=1

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Minor - Drop support for Swift 5.5 (#392) - Add `HPACKHeader.removeAll(keepingCapacity:)` (#393) ### SemVer Patch - Fix the test for `HPACKHeader.removeAll(keepingCapacity:)` on Android (#395, patch credit to @finagolfin) - Use the synchronous `NIOHTTP2Handler` multiplexer accessor for synchronous channel operations (#396) ### Other Changes - Update the allocation counts CI build script to drop support for Swift 5.5 and add Swift 5.9 (#397) ### SemVer Minor - Integrate the multiplexer into the `NIOHTTPHandler` (#377, #379, #380, #381, #382, #383, #384, #386) ### SemVer Patch - Avoid an allocation in the outbound frame buffer (#385) - Replace `estimatedFrameSize` with `flowControlledSize` and only count DATA frames (#387, #388) ### Other Changes - Make soundness check aware of 2023 (#378) - Add regression testing for docs and fix the issues. (#389) - Add docker-compose file for Swift 5.9 (#390) ### SemVer Patch - Soften errors when seeing inactive before active (#376) ### SemVer Patch - Correctly respect changes to HEADER_TABLE_SIZE (#374) ### SemVer Minor - Ensure that we fire channelActive and channelInactive in order (#373) ### SemVer Patch - Better handle writes issued with already completed promises (#372) ### SemVer Patch - Content-Length errors shouldn't crash (#371) ### SemVer Minor - Verify content length is not negative (#361) - Provide an iterator for header values (#362) ### SemVer Patch - Verify all content-length header values match (#360) - Make FramePayload.Data class-backed (#365) - Ignore content-length for HEAD requests and 304 responses (#369) ### Other Changes - Add .spi.yml for Swift Package Index DocC support (#363) - Add Swift 5.8 CI and update nightly CI to Ubuntu 22.04 (#366) - Point docs to Swift Package Index (#367) - Remove Jazzy doc generation (#368) - Update allocation limits (#370) ### SemVer Patch - Replace `NIOSendable` with `Sendable` (#358) ### Other Changes - Remove `#if compiler(>=5.5)` (#357) ### SemVer Minor - Raise minimum supported Swift version from 5.4 to 5.5 (#355) ### SemVer Patch - Better GoAWAY error (#354) ### Other Changes - Use Docc for documentation (#351) - Validate missing imports in CI (#352) - Update allocation limits (#356) ### SemVer Patch - Use `swift-atomics` instead of `NIOAtomics` (#350) ### Other Changes - Use 5.7 nightlies (#348)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Minor - Drop Swift 5.5 (#425) ### SemVer Patch - Use underscore version of `NIOPreconcurrencySendable` to silence warning (#427) ### SemVer Patch - Update BoringSSL to abfd5ebc87ddca0fab9fca067c9d7edbc355eae8 (#424) ### Other Changes - Use #fileID/#filePath instead of #file (#408) - Add .spi.yml for Swift Package Index DocC support (#410) - Add Swift 5.8 CI and update nightly CI to Ubuntu 22.04 (#415) - Point docs to Swift Package Index (#416) - Remove Jazzy doc generation (#417) - Fix the docs and add infrastructure for CI-ing it (#422) - Add docker-compose file for Swift 5.9 (#423) ### SemVer Minor - Raise minimum supported Swift version from 5.4 to 5.5 (#401) - Remove `Package.swift` for Swift 5.4 (#403) ### SemVer Patch - Replace Lock with NIOLock (#400) - Update BoringSSL to cab31f65f1ad6e6daca62e95b25dd6cd805fce0b (#402) - Update BoringSSL to b819f7e9392d25db6705a6bd3c92be3bb91775e2 (#406) ### Other Changes - Remove `#if compiler(>=5.5)` (#404) - Replace `NIOSendable` with `Sendable` (#405) ### SemVer Patch - Update BoringSSL to 8462a367bb57e9524c3d8eca9c62733c63a63cf4 (#399) ### Other Changes - Remove giant write test (#398) ### SemVer Minor - Adopt `Sendable` (#391, #392, #395, #397) ### SemVer Patch - Store internal error file and line number information in error wrappers (#393) ### Other Changes - Use DocC for documentation (#390) - Update expired certs for CA name test. (#394) - Validate missing imports in CI (#396) ### SemVer Minor - Add TLS-PSK Support (#369, patch credit to @agnosticdev) ### SemVer Patch - Tolerate massive writes (#384, #385) - Add sendCANameList to best effort functions. (#386) ### Other Changes - Update the expired leaf certificate (#383) - Invoke `additionalPeerCertificateVerificationCallback` with peer certificate (#387) - Make `NIOSSLCertificate._subjectAlternativeNames()` return type non-optional (#389) ### SemVer Patch - Unbuffer reads after handshake (#379) ### SemVer Patch - Include file path in `IOError`s thrown by `fopen` (#375) - Update BoringSSL to c239ffd0552179f358de31517391679e9b62ccd3 (#378) ### Other Changes - Use the 5.7 nightlies (#371) - Remove `try` from Server Example in README.md (#372) - Update BoringSSL vendor for Apple Silicon (#374) ### SemVer Minor - Add `NIOSSLCertificateExtensions` (#359) ### SemVer Patch - Port SecureBytes from Swift Crypto to use with TLS-PSK (#366, patch credit to @agnosticdev) - Add support for owned references to `NIOSSLObjectIdentifier` (#358) - Support additional certificate validation (#361) - Flush only after handshake (#362) - Update BoringSSL to 1e469e45a46ff580899cbef939babe02ad916c85 (#370) ### Other Changes - Parallel test fix for `TLSConfigurationTest` (#368, patch credit to @agnosticdev) - Update pod generation script (#363) - Remove build_podspec.sh (#365) ### SemVer Minor - Add `NIOSSLObjectIdentifier` (OID) type (#352) - Drop support for Swift 5.2 and 5.3 (#353) ### SemVer Patch - Update BoringSSL to f299342e38fd34b589604ef5b730623da13ee235 (#356) - Remove non-generic generic. (#357) ### Other Changes - Use SPM API diff checker (#351) - Fix warnings, that appeared after requiring Swift 5.4 (#355)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Minor - Drop Swift 5.5 support. (#140) ### SemVer Patch - Avoid sending window update messages if the connection is locally closed (#143) (#144, patch credit to @gaetanzanella) ### Other Changes - Add Android support (#134, patch credit to @finagolfin) - Update allocation counts (#135, #138) - Fix documentation and add support for CI-ing it (#137) - Add a docker-compose file for Swift 5.9 (#139) - Update the allocation counts CI build script to drop support for Swift 5.5 and add Swift 5.9 (#146) ### SemVer Patch - Remove some data-path CoW (#131) - Improve Sealed Box construction (#132) ### Other Changes - fix lost file handle error (#129, patch credit to @maartene) - Add Swift 5.8 CI and update nightly CI to Ubuntu 22.04 (#128) - Add initial allocation counter tests for SSH (#130) - Remove Jazzy doc generation (#133) ### SemVer Minor - Serialise SSH Public Key (#127) ### Other Changes - Add .spi.yml for Swift Package Index DocC support (#126) ### SemVer Minor - Adds support for custom transport protection algorithms (#97) - Raise minimum supported Swift version from 5.4 to 5.5 (#121) - Replace `NIOSSHSendable` with `Sendable` and remove it (#122) - Refactoring of the encryptPacket method (#123) ### Other Changes - Validate missing imports in CI (#120) - Use #fileID/#filePath instead of #file (#124) ### SemVer Patch - Use `swift-atomics` instead of `NIOAtomics` (#117) ### Other Changes - Use 5.7 nightlies (#115) - Use Docc for documentation (#118) ### SemVer Minor - Feature/userauth banners (#98, patch credit to @DominikHorn) - Add `PeerMaximumMessageLength` option for SSH child channels. (#101, patch credit to @gwynne) - Adopt `Sendable` on our public types (#106) - Drop support for Swift 5.2 and 5.3 (#113) ### SemVer Patch - Generate up to 8 random padding bytes at a time instead of 4 (#100, patch credit to @gwynne) - Support identification string without carriage return (#109, patch credit to @orobio) - fixes an issue where decodeFirstBlock can be called multiple times (#102) - Import concrete NIO modules (#105) ### Other Changes - Add 5.6 nightly CI. (#103, #104) - Add API breakages script from NIO (#111) - Fix warnings, that appeared after requiring Swift 5.4 (#114) ### SemVer Patch - Fix crash sending window increment after close (#95) ### Other Changes - Clean up incorrect comments and test behaviour (#96) ### SemVer Patch - Fix doc generation and jazzy version (#92) - Widen the pin on Crypto. (#93) ### Other Changes - Update to Swift 5.5 release in CI (#91) ### SemVer Patch - Use non-deprecated API for removing handlers (#90) ### SemVer Minor - Remove support for Swift 5.1 (#87) ### SemVer Patch - Add a benchmark for SSH throughput. (#83) - Use the ContiguousBytes functions for setting data (#84) - Update NIO dependency to 2.30.0 (#88) ### Other Changes - CI: Use 5.4 release instead of nightly and add. Swift 5.5 job (#81, #82)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This is a minor maintenance release fixing filename-related issues on Windows systems and bumping dependencies to the latest stable versions. ### Pull requests - https://github.com/apple/swift-collections-benchmark/pull/9 Make Paths Windows‐Compatible (by @SDGGiesbrecht) - https://github.com/apple/swift-collections-benchmark/pull/10 [library render]: Sanitize generated filenames (by @lorentey) - https://github.com/apple/swift-collections-benchmark/pull/13 Correct benchmark typo (by @mdznr) - https://github.com/apple/swift-collections-benchmark/pull/14 Bring dependencies to source-stable versions (by @WowbaggersLiquidLunch) - https://github.com/apple/swift-collections-benchmark/pull/16 Bump dependencies to latest revisions (by @lorentey) Full patch: https://github.com/apple/swift-collections-benchmark/compare/0.0.2...0.0.3 Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. ### Additions - The package now comes with a sample benchmark in the [`Documentation/Example`](https://github.com/apple/swift-collections-benchmark/tree/main/Documentation/Example) directory. (https://github.com/apple/swift-collections-benchmark/pull/6) ### Fixes - Swift Collections Benchmark now works more reliably on platforms with lower resolution timers (https://github.com/apple/swift-collections-benchmark/issues/4) - Resolved a build issue when building the package on iOS, watchOS and tvOS platforms. (https://github.com/apple/swift-collections-benchmark/issues/5) ### Source incompatible changes Note: Existing benchmark definitions created for 0.0.1 will continue to work without changes in this release. The package is no longer using `CGFloat`, `CGPoint`, `CGSize`, `CGRect` and `AffineTransform` in its public API; these types have been replaced with `Double`, `Point`, `Vector`, `Rectangle` and `Transform`, respectively. This change only affects the charting APIs (including option structs such as `Theme`); it doesn't affect benchmark definitions. (We also kept serialization formats compatible with the 0.0.1 release.) The `BenchmarkResults.Point` type has been renamed `Measurement`, with a deprecated typealias put in place for the original name. ### Pull requests (You can also find a full list of issues resolved and PRs merged in this release by looking at the [0.0.2 milestone](https://github.com/apple/swift-collections-benchmark/issues?q=milestone:0.0.2).) * #2: Update README.md (by @stephencelis) * #3: [Timer] Round zero measurements to the resolution of the timer (by @lorentey) * #6: Example for docs (by @heckj) * #8: Stop using CG types outside renderers (by @lorentey) Thank you to everyone who contributed to this release! Your bug reports, discussions and pull requests all help improve this package. This is the initial release.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### What's Changed - You can now generate documentation that includes [Swift symbols that extend other modules](https://forums.swift.org/t/document-extensions-to-external-types-using-docc/56060) when building with **Swift 5.8 or later**. This is an opt-in feature that can be used by passing the `--include-extended-types` flag: ```shell swift package generate-documentation --include-extended-types --target [target-name] ``` - You can now generate documentation that excludes compiler synthesized symbols provided by default implementations of protocol requirements. This is an opt-in, experimental feature that can used by passing the `--experimental-skip-synthesized-symbols` flag: ```shell swift package generate-documentation --experimental-skip-synthesized-symbols --target [target-name] ``` --- The `1.2.0` release includes contributions from @finestructure, @sofiaromorales, and @theMomax. Thank you! ### What's Changed - You can now generate documentation that includes [Swift Snippets](https://github.com/apple/swift-evolution/blob/main/proposals/0356-swift-snippets.md) when building with **Swift 5.7 or later**. --- The `1.1.0` release includes contributions from @A-N-uraag, @bitjammer, @compnerd, @denil-ct, @ethan-kusters, @franklinsch, @sofiaromorales, and @SRowley90. Thank you! Initial release.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Minor - Drop support for Swift 5.5 (#172) ### SemVer Patch - Use underscore version of `NIOPreconcurrencySendable` to silence warning (#173) ### Other Changes - Add docker-compose file for Swift 5.9 (#170) - Drop Topics section (#171) ### SemVer Minor - Expose multicast service type (#165) ### Other Changes - Use `#fileID`/`#filePath` instead of `#file` (#164) - Add `.spi.yml` for Swift Package Index DocC support (#166) - Point docs to Swift Package Index (#168) - Fix documentation and add infrastructure for CI-ing it (#169) - Add Swift 5.8 CI and update nightly CI to Ubuntu 22.04 (#167) ### SemVer Minor - Raise minimum supported Swift version from 5.4 to 5.5 (#158) - Remove `#if compiler(>=5.5)` (#161) - Fix Swift 5.5 (#162) - Allow retrieval of metadata from `NWConnection` (#163) ### SemVer Patch - Add missing availability annotation to NIOTSConnectionBootstrap (#160) ### SemVer Minor - Adopt `Sendable` (#155) - Allow services to be launched with existing NWConnection or NWListener objects (#156) ### SemVer Patch - Replace Lock with NIOLock (#157) ### SemVer Patch - Add defensive lifetime management for security metadata (#152) - Use `swift-atomics` instead of `NIOAtomics` (#153) ### Other Changes - Use 5.7 nightlies. (#151) - Use Docc for documentation (#154) ### SemVer Minor - Change `NIOTSNetworkEvent` initializers visibility to public level (#148, patch credit to @fananek) ### SemVer Patch - Don't close when waiting unless we were asked to. (#149) ### Other Changes - Update podspec script (#143) - Remove build_podspec.sh (#144) - Tweak `testConnectingInvolvesWaiting` to avoid invoking Private Relay (#146) ### SemVer Minor - Drop support for Swift 5.2 and 5.3 (#141) ### Other Changes - Add 5.6 nightly CI (#140) - Fix warnings, that appeared after requiring Swift 5.4 (#142) ### SemVer Patch - Explicitly retain timer source when scheduling tasks (#138) ### SemVer Patch - Clean up imports and dependencies. (#130)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. #### Changes - =fix Small typo in overloaded less-than operator for Node struct - thank you @dustinnewman! - Compiling SWIMNIOExample fails (logs included) -- this was due to a new API that we moved from SWIM's impl to upstream so we now had two definitions of the same API; fixed. - =metrics more precise emitting of pingRequest metrics #### Details Please refer to the [0.3.1 milestone](https://github.com/apple/swift-cluster-membership/milestone/6?closed=1) for a complete list of changes. #### Credits ``` commits added removed 3 1 49 Konrad `ktoso` Malawski 1 51 1 Dustin @dustinnewman 1 0 4 tomer doron ``` ### New features - the `SWIM.Instance` as well as example NIO implementation now emit metrics using [swift-metrics](https://github.com/apple/swift-metrics) ### Changes - This release includes a single commit since 0.2.0, enabling the metrics support. - There are no wire-compatibility concerns wrt. upgrading to 0.3.0 from 0.2.0 cluster nodes in a rolling upgrade. Please refer to the [0.3.0 milestone](https://github.com/apple/swift-cluster-membership/milestone/4?closed=1) for a complete list of changes. ``` commits added removed 1 1151 26 Konrad `ktoso` Malawski 1 2 1 Tomer Doron ``` Minor updates and cleanups to the SWIM APIs. Refer to the [0.2.0](https://github.com/apple/swift-cluster-membership/milestone/3?closed=1) milestone for more details. ### First release! In the first release we're including an implementation of the SWIM membership protocol. Please refer to <the docs> and <blog post> to learn more about it.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Add support for async/await (https://github.com/apple/swift-service-discovery/pull/39) - Adopt [swift-atomics](https://github.com/apple/swift-atomics) (https://github.com/apple/swift-service-discovery/pull/37) This package now requires Swift >= 5.3. This release doesn't contain any actual code changes.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Minor - Add the NFS3 protocol (#155) - Add `NIORequestResponseWithIDHandler` (#157) ### Other Changes - Fix documentation and add support for CI-ing it (#196) ### SemVer Minor - Make SynchronizedFileSink.close unavailable from async (#195) ### SemVer Minor - ServerQuiescingHelper no longer leaking promises (#192) ### SemVer Patch - Refactor `QuiescingHelper` to exhaustively iterate state (#193) ### SemVer Minor - Add HTTP1 proxy connect handler (#185) ### Other Changes - Add .spi.yml for Swift Package Index DocC support (#186) - Update generated test script from swift-nio (#188) - Add Swift 5.8 CI and update nightly CI to Ubuntu 22.04 (#190) - Remove Jazzy doc generation (#191) ### SemVer Minor - Raise minimum supported Swift version from 5.4 to 5.5 (#180) ### SemVer Patch - Replace `NIOSendable` with `Sendable` (#181) - Remove `#if compiler(>=5.5)` (#182) - Use #fileID/#filePath instead of #file (#184) ### Other Changes - Fix README.md (#183) ### SemVer Minor - Correctly validate the bounds of decompression (#177) ### Semver Patch - Correctly validate the bounds of decompression (#178) ### Semver Patch - Correctly validate the bounds of decompression (#179) ### SemVer Minor - Adopt `Sendable` (#172, #173, #174) ### SemVer Patch - Deprecate unused `cumulationBuffer` property for types conforming to `ByteToMessageDecoder` (#168) ### Other Changes - DocC support (#167, #169, #170) - Validate missing imports in CI (#171) ### SemVer Patch - Bump the lowest NIO version to 2.34.0 (#165) ### Other Changes - Use 5.7 nightlies (#164)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ## Initial 1.0 release After a very long period of incubation, including the development of language features ([SE-0311: Task Locals](https://github.com/apple/swift-evolution/blob/main/proposals/0311-task-locals.md)) and multiple iterations on exact shapes of the API to ensure least possible impact on instrumented code when tracing is disabled, we are happy to announce the first source stable release of swift-distributed-tracing! This package is an "API package", in the same way swift-log and swift-metrics are. This means that this package does not offer a Tracer implementation, but allows libraries to use this abstract API to instrument their code (e.g. http clients, distributed actors, gRPC or other) using tracing and once a tracer is bootstrapped by an end user, spans from given library are included in the distributed trace. ## Special thanks It should be noted that this project initially kicked off thanks to Swift participating in Google Summer of Code in 2020 ([initial repository announcement](https://forums.swift.org/t/announcement-swift-distributed-tracing-repositories-now-live/42497)), and would not have been possible without the relentless efforts of @slashmo sticking to the work and project even 3 years after GSoC concluded. Maturing such crucial "core" libraries for the server ecosystem takes time, and we've since gained multiple Swift language features which made this library possible, and we'd like to extend our thanks to everyone involved along the way. Thanks! ## Reference Documentation Getting started with distributed tracing can be somewhat daunting, so in order to explain how to adopt and what "kind of adopter" and aspect of APIs you should be looking at, the initial release features **comprehensive [reference documentation](https://swiftpackageindex.com/apple/swift-distributed-tracing/documentation/tracing)** in the form of docc documentation hosted on swiftpackageindex.com (or generated from the 1.0 sources). ## Notable changes since beta releases When upgrading from beta releases you might need to take care of the following changes: - The `Baggage` type, previously vended by the swift-distributed-tracing-baggage package is now known as **`ServiceContext`** and has also announced its 1.0 release. - Please refer to its release notes for further rationale on the rename: https://github.com/apple/swift-service-context/releases/tag/1.0.0 - It is possible to mock time using the tracing instant types - The library now splits its API between `LegacyTracer` which is Swift 5.6 compatible, and `Tracer` which requires Swift 5.7+ - The reason for this is that the APIs now return a concrete `Span` type from `startSpan` which allows avoiding existential boxing if using tracers explicitly. And such return type is only supported since Swift 5.7 because the `Span` protocol is a "protocol with associated types" Further, several small improvements have been made since the betas, but nothing has fundamentally changed in the APIs. ## Adoption plans We anticipate a few tracing implementations (most notably [slashmo/swift-otel](https://github.com/slashmo/swift-otel)) to soon release 1.0 compatible versions of libraries. We (as in the SSWG workgroup) will also collaborate with various client (e.g. http) and server projects to spread the adoption of this API in such way that enabling tracing should give a great ecosystem wide user experience. This process will take time, and we would love to see the community help with this process! If you have any questions about implementing tracers, or adopting them in your libraries or projects please don't hesitate to reach out on the forums: https://forums.swift.org/c/server/43 or in this repository's issues. ## What's Changed * startSpan should take tracepoint location by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/68 * Add .spi.yml for Swift Package Index DocC support by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/72 * Change 'landing' target to Tracing by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/74 * notes about LoggingContext by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/75 * Add CI for Swift 5.8 and update nightly to Ubuntu 22.04 by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/76 * Mark types Sendable by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/83 * Update CoC and add CONTRIBUTING file by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/87 * Allow for reading and mutating a span name by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/88 * Recording an error may carry attributes by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/90 * associated type Span, Tracer as short-hand, and *Protocol types by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/93 * Enable struct Spans with reference semantics; optimal NoopSpan by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/94 * remove not used docker configurations by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/96 * remove linux test shims by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/97 * Provide explicit set/get to avoid SpanAttributeConvertible wrapping by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/95 * Implement TracerClock and abstract away "now" by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/98 * Remove some unused/untested dead code by @fabianfett in https://github.com/apple/swift-distributed-tracing/pull/100 * Correct the default impl for startAnySpan for 5.7 by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/112 * Introduce top level withSpan; reclaim Tracer and Instrument for protocols by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/113 * Add nanoseconds to instant protocol by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/114 * Update CI by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/116 * Add nanoseconds to SpanEvent by @slashmo in https://github.com/apple/swift-distributed-tracing/pull/118 * remove clock protocol, use autoclosure "now" instant by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/120 * end() should take an autoclosure instant, not direct instant by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/122 * consider TracerSpan assoc type -> Span by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/111 * [Docs] Combined initial documentation work by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/121 * Adopt ServiceContext 1.0 by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/127 * Use 1.0.0 service-context by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/128 * Rename do not switch case by @fabianfett in https://github.com/apple/swift-distributed-tracing/pull/129 ## New Contributors * @fabianfett made their first contribution in https://github.com/apple/swift-distributed-tracing/pull/100 **Full Changelog**: https://github.com/apple/swift-distributed-tracing/compare/0.3.1...1.0.0 ## Important notes Please note that during the beta convergence period slight API changes are still happening. Please have a look at some of the type renames and move away from Clock types towards a `TracerInstant` and adjust tracer implementations accordingly. Important PRs changing APIs are: * Introduce top level withSpan; reclaim Tracer and Instrument for protocols by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/113 * remove clock protocol, use autoclosure "now" instant by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/120 * end() should take an autoclosure instant, not direct instant by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/122 * consider TracerSpan assoc type -> Span by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/111 In addition to that you can view the 13 closed issues on the [associated milestone](https://github.com/apple/swift-distributed-tracing/milestone/12?closed=1). ## Other changes * Remove some unused/untested dead code by @fabianfett in https://github.com/apple/swift-distributed-tracing/pull/100 * Correct the default impl for startAnySpan for 5.7 by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/112 * Add nanoseconds to instant protocol by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/114 * Update CI by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/116 * Add nanoseconds to SpanEvent by @slashmo in https://github.com/apple/swift-distributed-tracing/pull/118 ## New Contributors * @fabianfett made their first contribution in https://github.com/apple/swift-distributed-tracing/pull/100 **Full Changelog**: https://github.com/apple/swift-distributed-tracing/compare/1.0.0-beta.1...1.0.0-beta.2 ## First Beta release Hi everyone, this is the first beta release of the tracing API. We changed many things but believe we have arrived at the final API shapes of the library. Most notably, it is possible to stick to concrete types if necessary, abstract away the notion of time, as well as mutate span names in-flight before they are ended. No-op tracing also gained significant performance improvements, with `NoopSpan` becoming a struct and therefore not incurring reference counting traffic. And time is not going to be read unless the tracer decides to do so (allowing for no-op and inactive spans to avoid reading the system clock). ## Call to action: please try out the APIs in your tracers or adoption Please try out the APIs before we freeze them in a 1.0 release in the coming weeks. During the beta period, we are still able to perform any breaking or important changes before this API will become frozen for the foreseeable future. Please raise your issues on the github issue tracker. ### Updating from 0.3.x There have been a number of source breaking changes in order to achieve the ideal 1.0 shape of APIs since the 0.3.x series of this library. - `protocol Tracer` became `protocol TracerProtocol` - this was in order to introduce the `Tracer` namespace so that we can offer `Tracer.withSpan(...) { ... }` rather than the too long `InstrumentationSystem.tracer.withSpan(...) {` - the `startSpan` protocol requirement now accepts a `function` and `clock` parameters - please use the clock to obtain the timestamp of the events emitted by the tracer, rather than other time sources - by default the `DefaultTracerClock` will be used - a new `LegacyTracerProtocol` is introduced which is designed specifically to support Swift 5.6 clients - this protocol cannot make use of returning generic `Span` types, and has to erase them to `any Span`, which is why all APIs are phrased as `startAnySpan` - this protocol will be deprecated as soon as the library is able to require Swift 5.7, however it will not be removed in order to retain source compatibility with adopters who may have been using this API for a migration period. - if your library adopting (or implementing) distributed tracing CAN use Swift 5.7+, please implement the `TracerProtocol` directly; Implementations for the `Any` versions of APIs will be provided for you automatically, delegating to your `startSpan` implementation, so you do not need to implement any of the Legacy APIs. - documentation updates are incoming, including full guides for implementing and using tracers here: https://github.com/apple/swift-distributed-tracing/pull/69 ## Swift versions We are going to stick to the AsyncHTTP, gRPC and other core server library's Swift support strategy. This means that this package currently will support Swift: 5.6, 5.7, 5.8, and when 5.9 is released, we will drop support for 5.6. Supporting Swift 5.6 comes with a _significant_ burden for this project, and we want to drop it as soon as our adopters allow us to (i.e. AsyncHTTPClient and friends). We envision this library to be depended on by these projects and therefore must adhere to their minimum supported Swift policies. ## What's Changed * startSpan should take tracepoint location by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/68 * Add .spi.yml for Swift Package Index DocC support by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/72 * Change 'landing' target to Tracing by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/74 * notes about LoggingContext by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/75 * Add CI for Swift 5.8 and update nightly to Ubuntu 22.04 by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/76 * Mark types Sendable by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/83 * Update CoC and add CONTRIBUTING file by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/87 * Allow for reading and mutating a span name by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/88 * Recording an error may carry attributes by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/90 * associated type Span, Tracer as short-hand, and *Protocol types by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/93 * Enable struct Spans with reference semantics; optimal NoopSpan by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/94 * remove not used docker configurations by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/96 * remove linux test shims by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/97 * Provide explicit set/get to avoid SpanAttributeConvertible wrapping by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/95 * Implement TracerClock and abstract away "now" by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/98 **Full Changelog**: https://github.com/apple/swift-distributed-tracing/compare/0.3.1...1.0.0-beta.1 ## Changes - Added `withSpan` overload to accept a baggage from non-async code, but have the `operation` closure be `async` - Prepared docc setup, though not publishing yet. ## What's Changed * CI update by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/62 * DocC Setup by @yim-lee in https://github.com/apple/swift-distributed-tracing/pull/63 * +span additional withSpan to ease entering async world from non-async world by @ktoso in https://github.com/apple/swift-distributed-tracing/pull/64 ## New Contributors * @yim-lee made their first contribution in https://github.com/apple/swift-distributed-tracing/pull/62 **Full Changelog**: https://github.com/apple/swift-distributed-tracing/compare/0.3.0...0.3.1 Release with Sendable Updated: - `LoggingContext`-based propagation was replaced with automatic context propagation via task-locals (#52) - `SpanStatus` now conforms to `Equatable` (#46) - `OpenTelemetryTracingSupport` was removed (#53) --- For details on the changes please refer to the [0.2.0 milestone](https://github.com/apple/swift-distributed-tracing/milestone/3?closed=1) Updated: - `TracingOpenTelemetrySupport` now includes all semantic span attributes defined in Otel (0.7.0) (#38) Fixed: - Replaced all usage of `sanity` with `soundness` (#37) --- For details on the changes please refer to the [0.1.4 milestone](https://github.com/apple/swift-distributed-tracing/milestone/4) Updated: - `SpanStatus.CannonicalCode` has been removed in favor of `SpanStatus.Code` (#31) Fixed: - The context version of `withSpan` now delegates to the baggage version of this function (#36) - A "dead" link in the README file has been fixed (#35, credit to @MrCull) --- For details on the changes please refer to the [0.1.3 milestone](https://github.com/apple/swift-distributed-tracing/milestone/3) Fixed: - When using `withSpan`, `span.end()` is now correctly called on the happy path (#33, credit to @JensAyton) --- For details on the changes please refer to the [0.1.2 milestone](https://github.com/apple/swift-distributed-tracing/milestone/2) Same as 0.1.0 however fixed the dependency url in Package.swift to use https rather than git.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. This release adds modules for the recently published **FHIR R5** (`5.0.0`) release and the previous **FHIR R4B** (`4.3.0`) release. These can be accessed using `import ModelsR5` and `import ModelsR4B`, respectively. This is a maintenance release that addresses some issues and introduces small enhancements. - BREAKING CHANGES: fix duplicate code system names resulting in https://github.com/apple/FHIRModels/issues/11 - BREAKING CHANGES: regenerate R4 models to resolve https://github.com/apple/FHIRModels/issues/15 - Update _build_ models to 4.6.0-048af26 - Enhancement: make dates & times conform to `Comparable` and `ExpressibleAsNSDate` - Fix an issue where times with milliseconds were not proper ISO formatted in certain locales

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Minor - Implement Certificate Signing Request support (#59) - Add Policy Builder for constructing verifier policies (#79) - Gracefully fail `Extension` serialization (#80) ### SemVer Patch - Fix signature construction (#77) ### Other Changes - Fix OCSP serialisation and parsing tests (#81) ### SemVer Minor - Support PEM serialisation and parsing of `Certificate`, `Certificate.PublicKey` and `Certificate.PrivateKey` (#71) ### Other Changes - Fixed various typos in documentation (#73, #74, #75, #75, patch credit to @robo-fish) ### SemVer Patch - Fix windows build (#72, patch credit to @compnerd) ### Other Changes - Fix wrong variable in documentation (#70, patch credit to @LukasReschke) - Clean up the upToNextMinor (#69) ### SemVer Minor - Fix `SecureEnclave` issue in cmake build (#67, #68) ### SemVer Minor - Add support for using SecureEnclave.P256 (#55, patch credit to @jschlesser) - Add support for unwrapping public keys. (#60) - OCSP soft failure mode (#61) - Add API to construct a `SubjectKeyIdentifier` by hashing a `Certificate.PublicKey` (#64) ### SemVer Patch - Tweak the ECDSA signature representation (#50) - Fix name constraints parsing (#52) - Tolerate v1 certs without basic constraints (#53) - Add SPI support for disabling expiry checking in RFC5280Policy. (#54) - Fix `Sendable` warning in `OCSPVerifierPolicy.chainMeetsPolicyRequirementsWithoutDeadline` (#62) - Expose a CMSSignature type (#65) ### Other Changes - Documentation - Typos (#56, patch credit to @joey-gm) - Add docker-compose file for Swift 5.9 (#63) ### SemVer Minor - Follow casing from Swift API Design Guidelines (#46) - Add support for policing critical extensions (#47) ### SemVer Patch - Add BasicConstraints enforcement to RF5280Policy (#36) - Add support for handling domain name constraints. (#37) - Add support for IP address constraints. (#38) - Update Swift Crypto and fix RSA keys (#39) - Fix `Certificate.SerialNumber.init()` (#40) - Improve our handling of trailing periods. (#41) - Add support for name constraints on URIs (#42) - Build OCSP Response certificate chain and verify signature (#43) - Add directory name constraints. (#44) - Produce functional NameConstraints (#45) - Add leeway to the OCSP time verification (#48) ### Other Changes - Parallelise test cases (#49) Initial 0.1.0 release

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Minor - Adopt Sendable (#23) ### Other Changes - Use 5.7 nightlies (#24) - Use Docc for documentation (#25) ### SemVer Minor - Drop support for Swift 5.2 and 5.3 (#19) ### SemVer Patch - Remove redundant conformance constraints (#22) ### Other Changes - Add 5.6 main CI and nightly 5.7 (#17, #18 ) - Fix warnings, that appeared after requiring Swift 5.4 (#21) ### Changes - Rename a number of types and modules (#13) - Fixes for changes to the OSS Decimal type (#16) Initial release! This package will remain in zerover status until at least after the final RFC for HTTP structured headers ships. Once that happens we can consider freezing the API.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ### SemVer Patch - Fix bug in comparing Generalized and UTC Time (#30) ### SemVer Minor - Make `PEMDocument` `Hashable` and `Sendable` (#28) - Make GeneralizedTime and UTCTime Comparable. (#29) ### Other Changes - Clean up the upToNextMinor in the docs (#27) ### SemVer Minor - Changed scope of PEMDocument to public (#22, patch credit to @ekscrypto) - Add PEM support through `PEMRepresentable` (#26) ### Other Changes - Documentation - Typos (#24, patch credit to @joey-gm) - Clean up the upToNextMinor (#20) - Add docker-compose file for Swift 5.9 (#25) ### SemVer Minor * Add support for serializing raw bytes (#19) ## What's Changed * SET OF de/serialization in https://github.com/apple/swift-asn1/pull/12 **Full Changelog**: https://github.com/apple/swift-asn1/compare/0.5.0...0.6.0 ## What's Changed * Move to struct-backed error pattern by @Lukasa in https://github.com/apple/swift-asn1/pull/11 **Full Changelog**: https://github.com/apple/swift-asn1/compare/0.4.0...0.5.0 ## What's Changed * Set up CI #1 #2 #6 #7 #8 * Set up CMake build #9 * Add support for implicitly tagged optional fields #10 **Full Changelog**: https://github.com/apple/swift-asn1/compare/0.3.0...0.4.0

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Expose the paging token API from the C/C++ driver (https://github.com/apple/swift-cassandra-client/pull/22, credit to @erichmenge) - Make ssl.verifyFlag non-optional (https://github.com/apple/swift-cassandra-client/pull/15) Allow setting per statement request timeout (https://github.com/apple/swift-cassandra-client/pull/9) Includes: - Expose C* metrics (https://github.com/apple/swift-cassandra-client/pull/7) - Provide way to set cluster consistency (https://github.com/apple/swift-cassandra-client/pull/8)

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ## What's Changed * Update README.md by @hassila in https://github.com/apple/swift-statsd-client/pull/35 * DocC setup by @yim-lee in https://github.com/apple/swift-statsd-client/pull/36 * Allow client to send metrics to IPV6 addresses by @Palleas in https://github.com/apple/swift-statsd-client/pull/40 * Address deprecation warnings by @Palleas in https://github.com/apple/swift-statsd-client/pull/41 ## New Contributors * @hassila made their first contribution in https://github.com/apple/swift-statsd-client/pull/35 * @yim-lee made their first contribution in https://github.com/apple/swift-statsd-client/pull/37 * @Palleas made their first contribution in https://github.com/apple/swift-statsd-client/pull/40 **Full Changelog**: https://github.com/apple/swift-statsd-client/compare/1.0.0...1.0.1 First 1.0 release Introduces `MetricNameSanitizer` and enables it by default, allowing statsd-client to be used directly with Vapor apps (as their metric labels may include `:` which was causing trouble). See #21 for details. 3rd alpha release, fixes important issue with connection leak #14 second alpha release first alpha release

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. ## 1.0.0: `ServiceContext` Please note that the primary module vended by this library is `ServiceContext` which has changed from the library's pre-1.0 days. Please continue reading about migrating from the "Baggage" name type if you were using this library from before its 1.0 days. ## Migrating off the legacy type name: "Baggage" This package was initially developed for quite a while as the `swift-distributed-tracing-baggage` package and was used only by the [`swift-distributed-tracing` project](https://github.com/apple/swift-distributed-tracing). As time passed, more projects were making use of the baggage type and we decided to name this more generically. **Previously:** code using Baggage directly would be using it like this: ```swift import InstrumentationBaggage private enum FirstTestKey: BaggageKey { typealias Value = Int } var baggage = Baggage.topLevel // Note, from 1.0 this will emit deprecation warnings guard let value = baggage[FirstTestKey.self] else { return "no value" } return "value was: \(value)" ``` The above snippet continues to work, however it is deprecated upon release. Please adopt the new spelling of the type, which has the same capabilities as previous type: ```swift import ServiceContextModule private enum FirstTestKey: ServiceContextKey { typealias Value = Int } var context = ServiceContext.topLevel guard let value = context[FirstTestKey.self] else { return "no value" } return "value was: \(value)" ``` Everything about `ServiceContext` is the same as it was with `Baggage`, and the `InstrumentationBaggage` module now simply has a `typealias Baggage = ServiceContext` to ease migration in case you were using this type directly. The more generic name of "service context" allows developers to use this type for various context propagation needs, without necessarily binding it all with distributed tracing and the baggage terminology. ## What's Changed * Add .spi.yml for Swift Package Index DocC support by @yim-lee in https://github.com/apple/swift-service-context/pull/29 * Add CI for Swift 5.8 and update nightly to Ubuntu 22.04 by @yim-lee in https://github.com/apple/swift-service-context/pull/32 * Update CoC and add CONTRIBUTING file by @ktoso in https://github.com/apple/swift-service-context/pull/33 * Update CI by @yim-lee in https://github.com/apple/swift-service-context/pull/34 * Add _unsafeInheritExecutor to withValue convenience func by @ktoso in https://github.com/apple/swift-service-context/pull/35 * Add test coverage for using withValue inside an actor by @ktoso in https://github.com/apple/swift-service-context/pull/37 * Change package to ServiceContext; keep baggage compat module by @ktoso in https://github.com/apple/swift-service-context/pull/38 * Readme update for 1.0 by @ktoso in https://github.com/apple/swift-service-context/pull/39 **Full Changelog**: https://github.com/apple/swift-service-context/compare/0.4.1...1.0.0 ## What's Changed * Fix missing static keyword by @ktoso in https://github.com/apple/swift-distributed-tracing-baggage/pull/28 **Full Changelog**: https://github.com/apple/swift-distributed-tracing-baggage/compare/0.4.0...0.4.1 ## What's Changed * DocC setup by @yim-lee in https://github.com/apple/swift-distributed-tracing-baggage/pull/25 * Add support for Swift 5.1 (5.0 impossible due to compiler bug) by @slashmo in https://github.com/apple/swift-distributed-tracing-baggage/pull/26 * + convenience APIs since most people will never use the underlying `current` value by @ktoso in https://github.com/apple/swift-distributed-tracing-baggage/pull/27 ## New Contributors * @yim-lee made their first contribution in https://github.com/apple/swift-distributed-tracing-baggage/pull/25 **Full Changelog**: https://github.com/apple/swift-distributed-tracing-baggage/compare/0.3.0...0.4.0 Baggage is `Sendable`. Same as 0.2.1, no Sendable requirement - this is introduced now in 0.3.0 Fixed Sendable conformances for older OSes Updates: - Update SwiftFormat to 0.48.11 (#14) - Update installation guide to use 0.2.0 📖 (#15) --- For details on the changes please refer to the [0.2.1 milestone](https://github.com/apple/swift-distributed-tracing-baggage/milestone/3) Updated: - **Breaking**: Removed `LoggingContext` and dependencies, now includes `Baggage` directly in new `InstrumentationBaggage` module (#13) --- For details on the changes please refer to the [0.2.0 milestone](https://github.com/apple/swift-distributed-tracing-baggage/milestone/2) Same as 0.1.0 however fixed the dependency url in Package.swift to use https rather than git. Initial release

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. - add missing deps #47 - allow more TSC versions Be compatible with TSC's accidental API break at 0.2.5

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Bugfixes: - Adds a missing setter for `DiscontinousSlice.subscript(bounds:)` - Prevents out-of-bounds assignment when using the multiple-range setter for `Collection.subscript(subranges:)` Initial release.

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days. Same as 0.1.0, just released for consistency. Initial release

The markdown parsing is broken/disabled for release notes. Sorry about that, I'm chasing the source of a crash that's been bringing this website down for the last couple of days.