Add release automation

[mtrezza]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Add release automation

• Add release issue labels
• Local auto-release dry-run
• Add auto-release workflow
• Modify PR template
• Remove PR branches (keep only main, gh-pages)
• Rename main to release branch

Feature / Enhancement Description

n/a

Example Use Case

n/a

Alternatives / Workarounds

n/a

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[cbaker6]

The only thing that needs to be bumped for the version is:

Parse-Swift/Sources/ParseSwift/ParseConstants.swift

Line 13 in b4bdfb1

static let version = "2.2.6"

The changelog was manually modified, but you have a way to handle that.

The rest is handled by the release.yml and scripts.

[mtrezza]

Sounds good, should be an easy one.

[mtrezza]

@cbaker6 Does this repo currently need a beta branch in your opinion? If not then changes would be merged into alpha (working branch) and then periodically (e.g. monthly) merged into release branch to produce a stable release. We have some other repos where also we "skip" the beta releases because the added effort is not worth the benefit.

[cbaker6]

I think it can skip beta

[mtrezza]

Ok, I'd also rename the main branch to release for consistency across repos, do you see any issues that need to be considered specifically for this repo?

[cbaker6]

The name changes of the branches seem fine

[mtrezza]

Great, I'll coordinate with you before changing anything.

[mtrezza]

Just to ask, if you want to push out releases quickly, we can also only use a release branch without a pre-release (alpha, beta) branch for the moment. We are currently doing that in the Parse Android SDK to bring it up-to-date and get feedback faster. Another advantage is obviously that we don't need to supervise the merging of alpha into release every month or so, port hotfixes between branches and handle possible divergence. It seems you are putting a lot of care into reviewing PRs before merging anyway, so if you think it's a better fit for the moment we can also omit pre-release branches here.

[cbaker6]

This sounds good to me

[mtrezza]

I shall finally take a stab at this to relieve you of manual releasing. Hopefully by the weekend this should be done, I'll keep you posted here.