-
-
Notifications
You must be signed in to change notification settings - Fork 875
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
Release 1.18.0 #1494
Release 1.18.0 #1494
Conversation
noobs2ninjas
commented
Apr 13, 2020
- Updated Changelog for 1.18.0
- Fixed a small issue with a info.plist giving the wrong minimum SDK version.
@TomWFox Hey could you look at my changelog and give me your opinion about how I did. Let me know if you think I got too much or too little. Also, is nextrelease from the new forum or has that been around for a little while. |
Also, I cant create tags for new versions on this page. Only like issue tags. https://github.com/parse-community/Parse-SDK-iOS-OSX/tags |
I'll give it a look. Next Release is something I'm trying out for automating releases notes but I wouldn't worry about it for this release. Although I would like to start labelling all merged PRs going forward to help with this. |
A tag will be created once the release is published through GitHub. |
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.
I'd like to switch things up to having changes under the headings 'New Features', 'Improvements' & 'Fixes'. I think it makes the changelog easier to read, especially if there are lots of entries. Sound ok?
(don't worry about the bottom section with CI changes that can stay as is)
@TomWFox Thanks for editing that. I see how you guys are formatting now. I'll try to do that the first time next release. So, not sure if you got the e-mail yet from Nikita over on bolts but it seems they will be pushing an updated release later today. Once that happens, I'll do a commit updating Carthage versions and our Podspec and then this pull request should be GTG to merge and release. |
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.
I’m happy with the changelog now.
The version in the Parse.podspec file needs to be bumped, not sure if there is any other places.
@TomWFox Figured I'd wait to bump version and update podspec and carthage for when I can update Bolts to 1.9.1 |
Might be worth getting this PR as ready as possible if you want to get this release out quickly. Also I think we need to take a good look at what what is going on in #1491; the second issue raised about the supported platforms has come up again today in another issue. |
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.
I've added some quick comments on consistency.
ParseFacebookUtils/ParseFacebookUtils.xcodeproj/project.pbxproj
Outdated
Show resolved
Hide resolved
ParseFacebookUtils/ParseFacebookUtils.xcodeproj/project.pbxproj
Outdated
Show resolved
Hide resolved
Ok, So for now I'm going to make all iOS targets. Dynamic or not 1,2. I am removing all Catalyst support. |
Newest release of Bolts is out! Got our podspec and carthage files ready to go. Got @TomWFox fix for iphonesimulator updated. All I need is for these tests to build as expected and we should be ready for 1.18.0 to me merged into master and released! |
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.
Looks great! 😍
Seems like the failing tests fail more consistently now. That's a very good thing. Not this release particularly, but compared to last year say. That was one of the problems trying to fix them; I couldn't reliably reproduce the failures. |
Thanks @drdaz. Ahh yes you're right - I thought the branch protection only required one approval but I guess it also requires no outstanding required changes. |
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.
Fabby dabby do dar, thanks for the hard work!
Btw @noobs2ninjas I changed the tag from "Version 1.18.0" to "1.18.0" because it was complaining... |
So not sure what is going on here - when I go to edit the draft release I get a 404 page. @drdaz can you access the page to publish the release? |
Yeah I can see it. Weird that you can't ^^ I'll pull the lever yeah? |
It looks like it doesn't like the name 'Version 1.18.0'. We should probably stick to something without spaces. EDIT: I see you already spotted that. I'll try fixing it and releasing. |
Ka-ching. 1.18.0 should be out ^^ |
Hey there was something we had to do to update the version in Cocoapods... anybody remember what? 😬 |
Thanks! @noobs2ninjas bumped the version in the podspec so it should be fine, let's see when the build finishes! The tagged release build is here btw |
The deploy failed 😭 we might just have to do a manual deploy. |
I can take a look in the morning. Haven’t been able to work on deploy scripts much since we haven’t done a deploy on parse in quite a while |
FWIW here is the explanation of the failure from the build logs...
|
lol frustrating. That was kinda the point of adding the deployment target to our PRs... to make sure this didn't happen. |
I ran |
Going to see if I can lint and validate. |
Whatever's gone wrong here, when we figure it out, we should add this to our test suite. |
I'm not sure how you would go about adding it to the test suite fully unless you clone the repo and setup a dummy cocoapod. |
Admittedly I wrote that without looking at what's actually going on. |
So you can force a repo update and get version 1.9.1 of bolts/tasks. But
then doing a trunk push times out due to no response. If you add verbose
then the log gets too full and it kills the task. If you go to the circle
CI cocoapods build you can see why. Now there is a new macOS environment
that comes out that includes cocoapods 1.9.1 but that’s going to require me
to update all the freaking simulators again.
Oh forgot to mention the reason this is an issue to begin with is because
the 1.7.2 trunk spec is finalized and now it will be dynamically making
them. God this drives me nuts. Wish we could just switch to circle
completely.
…On Sat, Apr 18, 2020 at 12:09 PM Darren Black ***@***.***> wrote:
Admittedly I wrote that without looking at what's actually going on.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1494 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA2BOX53QVHZX7T35VU36TTRNHNC5ANCNFSM4MHBGDDQ>
.
|