Chris McGee
Chris McGee
@ADKaster a workaround for now might be to ask swiftly where the currently in-use toolchain is located: ``` swiftly use --print-location ``` And then construct a PATH without swiftly, and...
@FranzBusch thanks for reporting this. There was a fix for the error message unwrapping that was merged into the main branch after the cut of the 0.4.0-dev release that should...
@swift-server-bot test this please
@swift-server-bot test this please
@swift-server-bot test this please
I try to be careful when adding more dependencies. It feels like swiftly should try to minimize them. Should we add a new dependency for something that we already have,...
@swift-ci test macOS
@swift-ci test macOS
I'm closing this for now since there's no real urgency to aligning swiftly more with the sermver spec. We have already bumped the swiftly version to a 0.4.0 prerelease version.
@swift-ci test macOS