-
Notifications
You must be signed in to change notification settings - Fork 151
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
Moving the UI part to a separate subspec #16
Conversation
The
|
@@ -1,6 +1,6 @@ | |||
Pod::Spec.new do |s| | |||
s.name = "Concorde" | |||
s.version = "0.1.0" | |||
s.version = "0.1.1" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you remove this change? I prefer doing the version bump as its own separate change later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Allright, I didn't know podspecs could be updated therefore I created a new version.
LGTM except for the one comment, thanks for the PR! The warnings were indeed there already. |
Even though the version number is unchanged, are you still able to publish the new version of the podspec? We don't support swift yet on our project you see. |
No, but I'll update the version number as part of my normal release workflow after this has been merged. |
Keeping both Core and UI as default subspecs
Squashed |
Awesome, thanks for the contribution! |
Keeping both Core and UI as default subspecs