parse-community
Add release-automation
New Feature / Enhancement Checklist
- [x] I am not disclosing a vulnerability.
- [x] I am not just asking a question.
- [x] I have searched through existing issues.
Current Limitation
Releases are still done manually.
Feature / Enhancement Description
Add release automation.
Example Use Case
n/a
Alternatives / Workarounds
Manual release
Thanks for opening this issue!
- 🎉 We are excited about your ideas for improvement!
![parse-github-assistant[bot] avatar](https://avatars.githubusercontent.com/in/136195?v=4 "Published by a pub.dev verified publisher"){kind=small}
@drdaz I haven't done a release in this repo yet, could you describe the manual process currently, so we can see how to automate these steps?
Sure.
- Make a release branch + PR
- Update version numbers:
bundle exec rake package:set_version\[X.X.X\] - Update Changelog
- Tag release & push tag
- Add notes to releases page on GitHub
I... I think that's it. Often the LiveQuery lib needs it's podfile updating too.
Thanks! So all the version numbers are updated with that single command? That means that aside from the changelog there are no manual edits, correct?
Often the LiveQuery lib needs it's podfile updating too.
What are these updates?
Thanks! So all the version numbers are updated with that single command? That means that aside from the changelog there are no manual edits, correct?
Generally yeah, assuming no last-minute tweaks. I usually dump the root folder in VSCode and search for the old version number after the script is run, just to make sure.
Often the LiveQuery lib needs its podfile updating too.
What are these updates?
The version number of the Parse iOS SDK library in the podfile typically. Cocoapods often wants to select the previous version (even though it's specced using ~> notation).
EDIT: So that notation looks like it only keeps up with patch updates, not minor. So we probably lose the connection when we update the minor version in this repo.
Got it, I think we can make a script that updates all the version numbers and we should be good. Maybe @cbaker6 also has some input here?
Is this a thing that's happening Really Soon™️? Or should I manually create this release? 🙂
I'm looking into auto-release over the next days. If you need it urgently, I can manually release.
@drdaz I see that you are an owner on cocoapods. Could you add a new owner to there? I would send you the email via Slack if you are there.
@mtrezza I can give it a shot, but I can't get into Slack. The 2FA emails just aren't getting to me 🤔
Any other channels?
I think it would be good to get you on Slack somehow if that's possible. The release automation PR is ready and it would be good if you could stand-by on Slack for merging, in case there are any glitches. We may have to un-publish from cocoapods if things go wrong. It worked locally but you never know.
There's an invite elsewhere I've clicked on. I'm sure I've been in there before.
The auth just isn't working right now I think.
I don't think there's a publicly available Slack invite at the moment, they usually expire, so invite is only on a per-user basis now. You can try this link: https://join.slack.com/t/parseopensource/shared_invite/zt-8w385vtf-gIxfSqORSyoK6RO~y3bHZA
The assets I added back in releases starting from 1.19.2 are missing from the auto-release:
1.19.3
1.19.2
Re-opening, as we need to verify the assets and pods were built correctly before closing this.
@cbaker6 @drdaz could you take a look whether the GitHub release assets and the cocoapods (still building) are fine?
I left this comment to speed up the cocoa pod release: https://github.com/parse-community/Parse-SDK-iOS-OSX/pull/1632#discussion_r753868927
@mtrezza Can we close this? I found that assets comment you where talking about https://github.com/parse-community/Parse-SDK-iOS-OSX/issues/1628#issuecomment-974911439
