Skip to content

VertexCore 1.1.1

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Sep 17:36
· 0 commits to c7f726d110c1a0a15cbdee8a2046d84e835f01c1 since this release
6a2a8f0

VertexCore 1.1.1 is a small backwards-compatible maintenance release focused on cleaner persisted JSON output and internal build improvements while keeping the existing 1.1.x compatibility baseline unchanged.

What's New

  • JSON payloads written through the central JsonCodec are now pretty-printed for improved readability

  • Existing compact JSON remains fully readable and requires no migration

  • Maven dependency and plugin versions have been centralized

  • Maven compiler and shade configuration has been cleaned up and updated

  • Shaded runtime dependencies are now explicitly defined

  • Obsolete autonomous development documentation and retired NexusVault compatibility infrastructure have been removed

  • No intentional breaking changes were made to the public VertexCore 1.x API

Compatibility

Environment | Status -- | -- Paper 1.21.4 / Java 21 | ✅ Verified Paper 26.2 / Java 25 | ✅ Verified

VertexCore is compiled against the Paper 1.21.4 API and targets compatibility through Paper 26.2.

The same VertexCore JAR is runtime-tested at both compatibility endpoints.

Paper 26.1+ requires Java 25 on the server.

Verification

The final release artifact has passed:

  • ✅ Maven build and tests on Java 21

  • ✅ JSON serialization and backwards-compatibility regression tests

  • ✅ Paper 1.21.4 Build 232 runtime smoke test on Java 21

  • ✅ Paper 26.2 Build 121 runtime smoke test on Java 25

Release Artifact

vertexCore-1.1.1.jar

SHA256

ecaa0557136a03cce55d0a80b0b43532ec4e517519eeefcc045fc618502ce59d

The release artifact was built from the verified VertexCore development source and tested unchanged against both supported runtime endpoints.

Upgrading

VertexCore 1.1.1 can be used as a drop-in upgrade from VertexCore 1.1.0.

No configuration or database migration is required. Existing compact JSON data remains compatible, while newly written JSON payloads use the new formatted representation.