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

Release 1.18.0 #1494

Merged
merged 15 commits into from
Apr 16, 2020
Merged

Release 1.18.0 #1494

merged 15 commits into from
Apr 16, 2020

Conversation

noobs2ninjas
Copy link
Member

  • Updated Changelog for 1.18.0
  • Fixed a small issue with a info.plist giving the wrong minimum SDK version.

@noobs2ninjas noobs2ninjas linked an issue Apr 13, 2020 that may be closed by this pull request
@noobs2ninjas
Copy link
Member Author

@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.

@noobs2ninjas
Copy link
Member Author

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

@TomWFox
Copy link
Contributor

TomWFox commented Apr 13, 2020

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.

@TomWFox
Copy link
Contributor

TomWFox commented Apr 13, 2020

A tag will be created once the release is published through GitHub.

Copy link
Contributor

@TomWFox TomWFox left a 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 TomWFox added Release and removed 1.18.0 labels Apr 13, 2020
@noobs2ninjas
Copy link
Member Author

@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.

CHANGELOG.md Outdated Show resolved Hide resolved
@noobs2ninjas noobs2ninjas linked an issue Apr 13, 2020 that may be closed by this pull request
CHANGELOG.md Outdated Show resolved Hide resolved
@TomWFox TomWFox requested a review from drdaz April 13, 2020 20:17
Copy link
Contributor

@TomWFox TomWFox left a 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.

@noobs2ninjas
Copy link
Member Author

@TomWFox Figured I'd wait to bump version and update podspec and carthage for when I can update Bolts to 1.9.1

@TomWFox
Copy link
Contributor

TomWFox commented Apr 14, 2020

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.

Copy link
Member

@drdaz drdaz left a 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.

ParseUI/ParseUI.xcodeproj/project.pbxproj Outdated Show resolved Hide resolved
Parse/Parse.xcodeproj/project.pbxproj Outdated Show resolved Hide resolved
ParseUI/ParseUI.xcodeproj/project.pbxproj Outdated Show resolved Hide resolved
ParseUI/ParseUI.xcodeproj/project.pbxproj Outdated Show resolved Hide resolved
@noobs2ninjas
Copy link
Member Author

Ok, So for now I'm going to make all iOS targets. Dynamic or not 1,2. I am removing all Catalyst support.
Then before next release let's have a discussion and plan to add Catalyst support and also determine if we even need a "Dynamic" framework anymore.

@noobs2ninjas noobs2ninjas requested a review from TomWFox April 16, 2020 06:04
@noobs2ninjas
Copy link
Member Author

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!

@noobs2ninjas noobs2ninjas requested a review from drdaz April 16, 2020 06:10
@noobs2ninjas noobs2ninjas linked an issue Apr 16, 2020 that may be closed by this pull request
Copy link
Member

@drdaz drdaz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great! 😍

@drdaz
Copy link
Member

drdaz commented Apr 16, 2020

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.

@TomWFox
Copy link
Contributor

TomWFox commented Apr 16, 2020

Hold off before merging this @drdaz are you ok with #1497?

@drdaz
Copy link
Member

drdaz commented Apr 16, 2020

Hold off before merging this @drdaz are you ok with #1497?

Yup!

And I think you've got a block on the merge 🙂

@TomWFox
Copy link
Contributor

TomWFox commented Apr 16, 2020

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.

Copy link
Contributor

@TomWFox TomWFox left a 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!

@TomWFox
Copy link
Contributor

TomWFox commented Apr 16, 2020

Btw @noobs2ninjas I changed the tag from "Version 1.18.0" to "1.18.0" because it was complaining...
Screenshot 2020-04-16 at 16 46 53

@TomWFox TomWFox merged commit 09815dc into master Apr 16, 2020
@TomWFox TomWFox deleted the release-1.18.0 branch April 16, 2020 16:15
@TomWFox
Copy link
Contributor

TomWFox commented Apr 16, 2020

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?

@drdaz
Copy link
Member

drdaz commented Apr 16, 2020

Yeah I can see it. Weird that you can't ^^

I'll pull the lever yeah?

@drdaz
Copy link
Member

drdaz commented Apr 16, 2020

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.

@drdaz
Copy link
Member

drdaz commented Apr 16, 2020

Ka-ching. 1.18.0 should be out ^^

@drdaz
Copy link
Member

drdaz commented Apr 16, 2020

Hey there was something we had to do to update the version in Cocoapods... anybody remember what? 😬

@TomWFox
Copy link
Contributor

TomWFox commented Apr 16, 2020

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

@TomWFox
Copy link
Contributor

TomWFox commented Apr 16, 2020

The deploy failed 😭 we might just have to do a manual deploy.

@noobs2ninjas
Copy link
Member Author

noobs2ninjas commented Apr 16, 2020

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

@TomWFox
Copy link
Contributor

TomWFox commented Apr 16, 2020

FWIW here is the explanation of the failure from the build logs...

Resolving dependencies of
-> Parse (1.18.0)
- ERROR | [iOS] unknown: Encountered an unknown error (Unable to find a specification for Bolts/Tasks (~> 1.9.1) depended upon by Parse/Core

You have either:

  • out-of-date source repos which you can update with pod repo update or with pod install --repo-update.
  • mistyped the name or version.
  • not added the source repo that hosts the Podspec to your Podfile.

Note: as of CocoaPods 1.0, pod repo update does not happen on pod install by default.

@drdaz
Copy link
Member

drdaz commented Apr 16, 2020

lol frustrating. That was kinda the point of adding the deployment target to our PRs... to make sure this didn't happen.

@noobs2ninjas
Copy link
Member Author

I ran pod repo update as part of the script. Still same issue. I know bolts/tasks is available to cocoapods at that version because I just added it to a project and ran pod install and it gets back 1.9.1. However, I did have to run pod repo update first. So, not sure why its not working when I do it on the publish script.

@noobs2ninjas
Copy link
Member Author

Going to see if I can lint and validate.

@drdaz
Copy link
Member

drdaz commented Apr 18, 2020

Whatever's gone wrong here, when we figure it out, we should add this to our test suite.

@TomWFox
Copy link
Contributor

TomWFox commented Apr 18, 2020

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.

@drdaz
Copy link
Member

drdaz commented Apr 18, 2020

Admittedly I wrote that without looking at what's actually going on.

@noobs2ninjas
Copy link
Member Author

noobs2ninjas commented Apr 19, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants