Skip to content

build: Release #10010

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.

Sign up for GitHub

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

Closed
parseplatformorg wants to merge 4 commits into from
+270 −248
Closed

build: Release #10010

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
774cc54
refactor: Bump @semantic-release/github from 11.0.2 to 11.0.3 (#9789)
dependabot[bot] Dec 25, 2025
69da472
docs: Add frozen LTS branch info to CONTRIBUTING guide (#10008)
mtrezza Jan 16, 2026
82e0d3a
refactor: Bump commander from 13.1.0 to 14.0.2 (#9992)
dependabot[bot] Jan 17, 2026
6c492c6
empty commit to trigger CI
github-actions[bot] Jan 17, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -605,6 +605,8 @@ This creates a risk that a vulnerability is indirectly disclosed by publishing a

While the current major version is published on branch `release`, a Long-Term-Support (LTS) version is published on branch `release-#.x.x`, for example `release-4.x.x` for the Parse Server 4.x LTS branch.

Only the previous major version is under LTS. Older major versions are no longer maintained and their `release-#.x.x` branches are frozen; no further changes will be made. If you need features or fixes on an older branch, fork it and backport changes in your own branch.

### Preparing Release

The following changes are done in the `alpha` branch, before publishing the last `beta` version that will eventually become the major release. This way the changes trickle naturally through all branches and code consistency is ensured among branches.
Expand Down
Loading
Loading