-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Closed
Labels
block:majorNeeds to be resolved before next major release; remove label afterwardsNeeds to be resolved before next major release; remove label afterwardsstate:breakingBreaking change requires major version increment and `BREAKING CHANGE` commit messageBreaking change requires major version increment and `BREAKING CHANGE` commit messagetype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature
Description
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
With release of Parse Server 6.
- Parse Server 4 LTS branched will be archived (no future commits)
- Parse Server 5 branch moves to LTS
Feature / Enhancement Description
- Create LTS branch release-5.x.x
- Update CI on branch
release-5.x.x
for LTS - Lock branch
release-4.x.x
via branch protection rule; no further commits allowed
In addition made changes so that future LTS branches won't require manual code changes and can follow the simplified process described in Publishing Major Release (Yearly Release):
- ci: Add auto-release LTS branch detection #8325
- ci: Add auto-release LTS branch detection #8326
- ci: Update release workflow for LTS branches #8327
Example Use Case
n/a
Alternatives / Workarounds
n/a
Metadata
Metadata
Assignees
Labels
block:majorNeeds to be resolved before next major release; remove label afterwardsNeeds to be resolved before next major release; remove label afterwardsstate:breakingBreaking change requires major version increment and `BREAKING CHANGE` commit messageBreaking change requires major version increment and `BREAKING CHANGE` commit messagetype:featureNew feature or improvement of existing featureNew feature or improvement of existing feature