# Announcing Swift 6.3.2 **URL:** \ **Category:** Announcements\ **Created:** [May 13, 2026, 3:30pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698 "2026-05-13T15:30:00Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![mishal\_shah](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mishal_shah/32/247_2.png) [@mishal\_shah](https://forums.swift.org/u/mishal_shah)\ **Post date:** [May 13, 2026, 3:30pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/1 "2026-05-13T15:30:01Z")
We are happy to announce the release of Swift 6.3.2. **Install Swift Toolchain** - Install via Swiftly `swiftly install 6.3.2` or `swiftly install latest` - Download toolchain directly from [Install Swift | Swift.org](http://swift.org/install) - Docker images will be available on [hub.docker.com/\_/swift](http://hub.docker.com/_/swift) soon ([PR#21458](https://github.com/docker-library/official-images/pull/21458)) - Swift toolchain will be available on WinGet soon ([PR#373862](https://github.com/microsoft/winget-pkgs/pull/373862)) - Xcode 26.5 contains Swift 6.3.2 **Release Notes** - **Swift** - When using C++ interoperability on Linux, allow importing C++ libraries that use C++23 headers such as `` ([#88646](https://github.com/swiftlang/swift/pull/88646)) - **LLDB** - Improved error handling when Python cannot be found on Windows ([#12698](https://github.com/swiftlang/llvm-project/pull/12698)) - **Swift Package Manager** - When using resources, allow the Bundle.module to be accessed from outside the MainActor ([#9850](https://github.com/swiftlang/swift-package-manager/pull/9850)) - Several fixes related to Package Registry interactions ([#9993](https://github.com/swiftlang/swift-package-manager/pull/9993), [#9984](https://github.com/swiftlang/swift-package-manager/pull/9984), [#9968](https://github.com/swiftlang/swift-package-manager/pull/9968), [#9941](https://github.com/swiftlang/swift-package-manager/pull/9941), [#9926](https://github.com/swiftlang/swift-package-manager/pull/9926)) - **Swift Testing** - Fixed an issue causing exit tests to return invalid results when no standard output or error is produced ([#1695](https://github.com/swiftlang/swift-testing/pull/1695)) - Emits a warning when one of the testing library’s attribute macros, such as `@Test`, includes generic type parameters since they are unsupported. ([#1653](https://github.com/swiftlang/swift-testing/pull/1653)) - **libdispatch** - Changed dispatch worker thread names to “DispatchWorker”, instead of being based on the label of the root queue they are servicing ([#936](https://github.com/swiftlang/swift-corelibs-libdispatch/pull/936)) - **Swift Build** - When using resources, allow the Bundle.module to be accessed from outside the MainActor ([#1240](https://github.com/swiftlang/swift-build/pull/1240)) - **SourceKit-LSP** - Fixed an issue that could cause sourcekit-lsp to crash on Windows when using a `compile_commands.json` for build settings ([#2606](https://github.com/swiftlang/sourcekit-lsp/pull/2606)) - Introduced `forceResolvedVersions` configuration option, which is equivalent to SwiftPM’s `--force-resolved-versions`option. This can be used to ensure that background indexing treats `Package.resolved` as a lock file ([#2613](https://github.com/swiftlang/sourcekit-lsp/pull/2613)) ---
**Author:** ![MahdiBM](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mahdibm/32/45271_2.png) [@MahdiBM](https://forums.swift.org/u/MahdiBM)\ **Post date:** [May 13, 2026, 7:07pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/2 "2026-05-13T19:07:36Z")
I notice the long-awaited Amazon Linux 2023 images are now out too 🥳! > **[swift Tags | Docker Hub](https://hub.docker.com/_/swift/tags?name=6.3.2)** > > Docker Official Image swift Tags page `6.3.2-amazonlinux2023` / `6.3-amazonlinux2023` + `-slim` images ---
**Author:** ![taylorswift](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/taylorswift/32/43413_2.png) [@taylorswift](https://forums.swift.org/u/taylorswift)\ **Post date:** [May 13, 2026, 7:27pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/3 "2026-05-13T19:27:33Z")
i notice there is no `6.3.2` scheme in [swift/utils/update\_checkout/update-checkout-config.json at main · swiftlang/swift · GitHub](https://github.com/swiftlang/swift/blob/main/utils/update_checkout/update-checkout-config.json#L264) should there be? ---
**Author:** ![Cyberbeni](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/cyberbeni/32/46241_2.png) [@Cyberbeni](https://forums.swift.org/u/Cyberbeni)\ **Post date:** [May 13, 2026, 7:53pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/4 "2026-05-13T19:53:34Z")
The `docker.io/swift:6.3.2` image (and a couple other tags) only has arm64 variant. ---
**Author:** ![networkextension](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/networkextension/32/45274_2.png) [@networkextension](https://forums.swift.org/u/networkextension)\ **Post date:** [May 13, 2026, 8:34pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/5 "2026-05-13T20:34:23Z")
I need FreeBSD arm64 version ,I can setup CI env ,I have BSD box 16core [HoneyComb LX2K](https://www.solid-run.com/arm-servers-networking-platforms/honeycomb-servers-workstation/) ---
**Author:** ![mishal\_shah](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/mishal_shah/32/247_2.png) [@mishal\_shah](https://forums.swift.org/u/mishal_shah)\ **Post date:** [May 13, 2026, 8:43pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/6 "2026-05-13T20:43:04Z")
> [@taylorswift](#): > > i notice there is no `6.3.2` scheme in [swift/utils/update\_checkout/update-checkout-config.json at main · swiftlang/swift · GitHub](https://github.com/swiftlang/swift/blob/main/utils/update_checkout/update-checkout-config.json#L264) > > should there be? You should use the `--tag swift-6.3.2-RELEASE` option. Additionally, Swift 6.3.2 was released from the `release/6.3` branch, so you can also use that scheme too. ---
**Author:** ![macguru](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/macguru/32/22306_2.png) [@macguru](https://forums.swift.org/u/macguru)\ **Post date:** [May 18, 2026, 9:24pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/7 "2026-05-18T21:24:38Z")
It seems like Swift 6.3.1 is still the current release on the project’s GitHub page: [Releases · swiftlang/swift · GitHub](https://github.com/swiftlang/swift/releases) . There is a tag for 6.3.2 though [Release swift-6.3.2-RELEASE · swiftlang/swift · GitHub](https://github.com/swiftlang/swift/releases/tag/swift-6.3.2-RELEASE) . ---
**Author:** ![bastie](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/bastie/32/22636_2.png) [@bastie](https://forums.swift.org/u/bastie)\ **Post date:** [May 21, 2026, 4:34pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/8 "2026-05-21T16:34:53Z")
I`m not sure: are all these changes in Swift 6.3.2 really - I mean really really - BugFixes? It looks like somethink are more than patches and its feels wrong to provide this in a patch version 6.3.2 instead of 6.4 - or not? ---
**Author:** ![Jon\_Shier](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/jon_shier/32/921_2.png) [@Jon\_Shier](https://forums.swift.org/u/Jon_Shier)\ **Post date:** [May 21, 2026, 10:50pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/9 "2026-05-21T22:50:50Z")
Swift doesn't strictly follow semantic versioning. Though personally I'd consider them all fixes of one type or another. SourceKit-LSP's `forceResolvedVersions` is as close to a new feature I can see, but even that is just "fixing" its mismatched behavior vs. SPM. ---
**Author:** ![networkextension](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/networkextension/32/45274_2.png) [@networkextension](https://forums.swift.org/u/networkextension)\ **Post date:** [June 11, 2026, 7:53pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/10 "2026-06-11T19:53:43Z")
```swift % sh run-tests.sh === System === FreeBSD 14.4-RELEASE arm64 aarch64 === Test 1: hello_arm64 === Hello from Swift on FreeBSD arm64! arch check: arm64 ✓ sorted: [1, 1, 2, 3, 4, 5, 6, 9] [PASS] hello === Test 2: async_arm64 (Swift Concurrency) === concurrency works: [1, 4, 9, 16, 25, 36, 49, 64] [PASS] async swift@dpaa2:~/test/swift-arm64-test % uname -a FreeBSD dpaa2 14.4-RELEASE FreeBSD 14.4-RELEASE releng/14.4-n273675-a456f852d145 GENERIC arm64 ``` github repo [GitHub - networkextension/swift-freebsd: swift-freebsd · GitHub](https://github.com/networkextension/swift-freebsd) ---
**Author:** ![Lin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/lin/32/44031_2.png) [@Lin](https://forums.swift.org/u/Lin)\ **Post date:** [June 12, 2026, 12:03am UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/11 "2026-06-12T00:03:32Z")
This is huge, thanks for improving freebsd toolchain, this is very useful for small arm64 SBC ---
**Author:** ![networkextension](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/networkextension/32/45274_2.png) [@networkextension](https://forums.swift.org/u/networkextension)\ **Post date:** [June 13, 2026, 11:45am UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/12 "2026-06-13T11:45:34Z")
start real test ![Screenshot 2026-06-13 at 19.44.15](https://global.discourse-cdn.com/swift/original/3X/e/1/e12544790722509712eed0a55698b4d51c1265b8.jpeg) ---
**Author:** ![networkextension](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/networkextension/32/45274_2.png) [@networkextension](https://forums.swift.org/u/networkextension)\ **Post date:** [June 13, 2026, 12:06pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/13 "2026-06-13T12:06:44Z")
# [Swift on FreeBSD arm64 first package on github](https://github.com/networkextension/swift-freebsd) ---
**Author:** ![Finagolfin](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/finagolfin/32/34388_2.png) [@Finagolfin](https://forums.swift.org/u/Finagolfin)\ **Post date:** [June 13, 2026, 1:02pm UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/14 "2026-06-13T13:02:32Z")
Nice, have you tried running the compiler validation suite when natively building on FreeBSD AArch64, by passing the `-T` flag to `build-script` as [I showed here for linux AArch64](https://forums.swift.org/t/building-a-linux-aarch64-toolchain-on-macos-with-containerization/84347)? It would be great if you filed an issue with your test run results, as [I did here for Fedora 43 AArch64](https://github.com/swiftlang/swift/issues/88176) a couple months ago. ---
**Author:** ![networkextension](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/networkextension/32/45274_2.png) [@networkextension](https://forums.swift.org/u/networkextension)\ **Post date:** [June 15, 2026, 3:57am UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/15 "2026-06-15T03:57:17Z")
> > > Following up on @finagolfin's suggestion — here are the results of running the c…ompiler > validation test suite (\`build-script -T\`) on \*\*FreeBSD 14.4 / AArch64\*\*, built and tested > natively on the device. > > \## Environment > > | | | > |---|---| > | OS | FreeBSD 14.4-RELEASE, \`aarch64\` | > | Host | 16 cores, 64 GB RAM | > | Target triple | \`aarch64-unknown-freebsd14.4\` | > | swift | \`3f8c798cfe25bbb04f2bae2ec81a46259f5f637b\` | > | llvm-project | \`972b62858355d0714921cbf489de6598376e914a\` | > | swift-syntax | \`swift-DEVELOPMENT-SNAPSHOT-2026-02-02-a\` (\`edbbad24\`) | > | Build type | \`--release\`, \`--bootstrapping=hosttools\` | > > This is a 2nd-stage native build: a seed compiler was first cross-compiled on x86 FreeBSD, > then used to natively build the full compiler + stdlib + Foundation/Dispatch/XCTest/ > swift-testing from source on the AArch64 device. Details and the FreeBSD AArch64 build > patches: https://github.com/networkextension/swift-freebsd > > \## Results > > \`\`\` > Testing Time: 8106.19s > Total Discovered Tests: 21177 > Unsupported : 3283 (15.50%) > Passed : 17813 (84.11%) > Expectedly Failed : 53 (0.25%) > Failed : 26 (0.12%) > Unexpectedly Passed : 1 (0.00%) > \`\`\` > > 84% pass / 26 failures (0.12%) — FreeBSD AArch64 is in good shape. > > \## Failures (26), grouped > > \*\*Reflection / typeref (6)\*\* — likely the largest cluster: > \- \`Reflection/conformance\_descriptors.swift\` > \- \`Reflection/typeref\_decoding.swift\`, \`typeref\_decoding\_asan.swift\`, \`typeref\_decoding\_packs.swift\` > \- \`Reflection/typeref\_lowering.swift\`, \`typeref\_lowering\_packs.swift\` > > \*\*C++ interop stdlib (4)\*\*: > \- \`Interop/Cxx/function/default-arguments-multifile.swift\` > \- \`Interop/Cxx/stdlib/foundation-and-std-module.swift\` > \- \`Interop/Cxx/stdlib/import-cxx-math-ambiguities.swift\` > \- \`Interop/Cxx/stdlib/use-std-optional-lib.swift\` > > \*\*TSan (3)\*\*: > \- \`Sanitizers/tsan/libdispatch.swift\` > \- \`Sanitizers/tsan/norace-block-release.swift\` > \- \`Sanitizers/tsan/norace-deinit-run-time.swift\` > > \*\*Runtime unit tests (3)\*\*: \`SwiftRuntimeTests\` shards 10, 11, 12 / 16 > > \*\*Macros (2)\*\*: > \- \`Macros/expand\_on\_imported.swift\` > \- \`Macros/print\_clang\_expand\_on\_imported.swift\` > > \*\*Concurrency / Synchronization (2)\*\* — possibly a real atomics/concurrency issue worth a look: > \- \`Concurrency/Runtime/cancellation\_handler\_only\_once.swift\` > \- \`stdlib/Synchronization/Mutex/LockSingleConsumerStack.swift\` (its unit counterpart > \`\["concurrentPushes", "concurrentPushesAndPops"\]\` also fails; these tended to \*hang\* > rather than fail fast) > > \*\*Misc (6)\*\*: > \- \`IRGen/pic.swift\` > \- \`Interpreter/generic\_casts.swift\` > \- \`Runtime/subclass\_instance\_start\_adjustment.swift\` > \- \`SILGen/coroutine\_accessors\_back\_deployment\_abi.swift\` > \- \`Swift-validation :: Evolution/test\_coroutine\_accessors.swift\` > \- \`Swift-validation :: Sema/type\_checker\_perf/fast/swift\_docc.swift\` (perf threshold) > > 1 test \`Unexpectedly Passed\` (an \`XFAIL\` that passes on FreeBSD AArch64). > > \## Note on hangs / \`--lit-args\` > > A few tests (the TSan ones and the \`Synchronization\` Mutex/lock-free-stack stress tests) > \*\*hang\*\* rather than fail. \`build-script -T --lit-args="--timeout=300"\` did not appear to > propagate the per-test timeout to the validation \`lit\` invocation, so the run stalled on > them; I worked around it with an external watchdog that killed test processes exceeding a > CPU-time budget. If there's a supported way to pass a per-test timeout to the validation > suite via \`build-script\`, a pointer would be appreciated (and the propagation may be worth > fixing). > > Happy to dig into any specific failure, post full logs, or re-run with extra flags. Thanks > @finagolfin for the nudge. ---
**Author:** ![networkextension](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/networkextension/32/45274_2.png) [@networkextension](https://forums.swift.org/u/networkextension)\ **Post date:** [June 18, 2026, 3:23am UTC](https://forums.swift.org/t/announcing-swift-6-3-2/86698/16 "2026-06-18T03:23:54Z")
[Swift 6.3.2 arm64 FreeBSD native package](https://github.com/networkextension/swift-freebsd/releases/download/v0.4.0-6.3.2/swift-6.3.2-RELEASE-freebsd15-aarch64.tar.zst)Anyone want to help test ?