Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Set Carthage Swift version to 4.2 (Swift 4 + 5 compatibility) #47

Merged
merged 1 commit into from
Mar 6, 2019

Conversation

erikkerber
Copy link
Contributor

@erikkerber erikkerber commented Feb 20, 2019

Description

Update the Swift version to 4.2 in the Carthage support Xcode project

Motivation and Context

The current Xcode project specifies Swift 3. This will be incompatible with Swift 5 being released shortly in Xcode 10.2.

By specifying Swift 4.2, swift-html-entities will be compatible with both Swift 4.2 and Swift 5.

How Has This Been Tested?

Carthage build using Xcode 10.1 and Xcode 10.2 beta 3 as the set toolchains.

After reading below I will get a CLA form signed shortly!

Checklist:

  • I have submitted a CLA form
  • If applicable, I have updated the documentation accordingly.
  • If applicable, I have added tests to cover my changes.

@CLAassistant
Copy link

CLAassistant commented Feb 20, 2019

CLA assistant check
All committers have signed the CLA.

@erikkerber erikkerber changed the title Set Swift version to 4.2 (Swift 4 + 5 compatibility) Set Carthage Swift version to 4.2 (Swift 4 + 5 compatibility) Feb 20, 2019
@erikkerber
Copy link
Contributor Author

@djones6 Have any thoughts on this? That license CI step is stuck at yellow, not sure how to kick that over.

@ianpartridge ianpartridge merged commit 9c3c3a9 into Kitura:master Mar 6, 2019
@ianpartridge
Copy link
Contributor

Not sure but I've merged for you! Thanks for the PR.

@erikkerber erikkerber deleted the swift4 branch April 4, 2019 19:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants