Releases: swiftwasm/swift
Releases · swiftwasm/swift
swift-wasm-DEVELOPMENT-SNAPSHOT-2020-09-23-a
Merge pull request #1810 from swiftwasm/maxd/merge-master Resolve conflicts with upstream branch renaming
swift-wasm-5.3-SNAPSHOT-2020-09-23-a
Merge pull request #1773 from swiftwasm/wasi-module-5.3 Add WASI module to replace Glibc on WASI platform
swift-wasm-DEVELOPMENT-SNAPSHOT-2020-09-22-a
Merge pull request #1797 from swiftwasm/master [pull] swiftwasm from master
swift-wasm-DEVELOPMENT-SNAPSHOT-2020-09-21-a
Merge pull request #1789 from swiftwasm/expand-funding Add @kateinoigakukun to `FUNDING.yml`
swift-wasm-DEVELOPMENT-SNAPSHOT-2020-09-20-a
Merge pull request #1785 from swiftwasm/katei/merge-master-2020-09-20 Merge master 2020-09-20
swift-wasm-5.3-SNAPSHOT-2020-09-13-a
Merge pull request #1724 from swiftwasm/katei-merge-5.3 Upstream merge 5.3
swift-wasm-5.3-SNAPSHOT-2020-09-08-a
Merge pull request #1709 from kateinoigakukun/katei/fix-keypath-opt [WASM] Fix KeyPath optimization bug around signature match
swift-wasm-5.3-SNAPSHOT-2020-09-03-a
Merge pull request #1683 from swiftwasm/maxd/fix-sdk-paths Prioritize SDK paths in CMake find_ functions in 5.3 branch It looks like after https://github.com/actions/virtual-environments/commit/ff1423cd6f345ef56adcf8e3e8585908f742f740 was deployed, the [SR-12726](https://bugs.swift.org/browse/SR-12726) bug is now reproducible on GitHub Actions. It was fixed in upstream `master`, but wasn't applied to upstream `release/5.3`, I'm re-applying it to the release branch here.
swift-wasm-5.3-SNAPSHOT-2020-09-02-a
Merge pull request #1667 from swiftwasm/release/5.3 [pull] swiftwasm-release/5.3 from release/5.3
swift-wasm-5.3-SNAPSHOT-2020-08-28-a
Merge pull request #1635 from swiftwasm/maxd/5.3-merge Fix build issues in the 5.3 branch