Skip to content

feat(velocity): explain releases and snapshots - #829

Open
spa77k wants to merge 1 commit into
PaperMC:mainfrom
spa77k:docs/velocity-release-channels
Open

spa77k wants to merge 1 commit into
PaperMC:mainfrom
spa77k:docs/velocity-release-channels

Conversation

@spa77k

@spa77k spa77k commented Nov 13, 2026

Copy link
Copy Markdown
Contributor

Closes PaperMC/Velocity#1884

Adds a short "Releases and snapshots" section to the Velocity getting-started page, so "the latest stable version" has a clear meaning. It covers what electronicboy and WouterGritter explained in the issue:

  • releases (e.g. 4.3.1) are stable, -SNAPSHOT versions are beta with no compatibility promises within a snapshot cycle
  • an x.y.z-SNAPSHOT does not promise an x.y.z release; a release that follows can be x.y.z or higher
  • semantic versioning applies to release versions, with the caveat that Velocity is not a library

The stable/beta split matches the Fill API channels (e.g. 4.3.1 build 45 is STABLE, 4.3.2-SNAPSHOT builds 46–49 are BETA).

I left out whether older release lines are supported and whether new Minecraft versions always land in a release, since those were not answered in the issue. Happy to add them if you can confirm the policy.

@github-actions

github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
papermc-docs ✅ Ready (View Log) Visit Preview efd1727

This branch was successfully deployed

1 active deployment
Preview — efd17272 Deployed Nov 13, 2026 by github-actions[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Document the release vs. SNAPSHOT policy since Velocity 4.x

1 participant