Jarock changelog

The complete release history is maintained in the repository's Keep a Changelog document.

changelog
Open CHANGELOG.md on GitHub
The root scripts/version.txt remains the single source for the current project version.

Loading changelog from repository…

Recent project direction

Area	Current direction
Loader	Fabric first, NeoForge fallback, Forge only after official verification.
Runtime	Generated runtime stays local; repository scripts and templates are tracked.
Launch	One repository-root `start-server.bat` entry point.
Release channel	Beta prereleases use the `-beta` suffix and plain semantic release tags.
Website	Static multipage utility catalogue deployed through GitHub Pages.

Release automation

Commits beginning with v can trigger the existing autorelease workflow when version and changelog requirements are satisfied. Release tags are generated from the plain semantic version stored in scripts/version.txt.