Skip to content

Wiki

Type at least 2 characters

    ↑↓ navigate↵ openEsc close

    Semantic versioning

    referenceUnderstand version numbers used by Tegra and by modpacks published on the platform.semver semantic versioning version major minor patch betaen

    Tegra uses semantic versioning, usually written as MAJOR.MINOR.PATCH, for example 2.4.1.

    What each number means

    Section titled “What each number means”
    • MAJOR (2): a large change that can require adaptation or break compatibility.
    • MINOR (4): new features compatible with the current line.
    • PATCH (1): fixes and adjustments without incompatible new features.

    Therefore, 2.4.1 is newer than 2.4.0, and 2.5.0 adds something beyond the 2.4 line.

    Which number to increase

    Section titled “Which number to increase”

    Use the type of the largest change included in the update:

    • Incompatible change: 8.2.1 → 9.0.0. Use it when removing essential mods, changing the pack foundation, or requiring a new world.
    • Compatible new content: 8.2.1 → 8.3.0. Use it when adding mods, quests, or features while preserving existing worlds and installations.
    • Fix or adjustment: 8.2.1 → 8.2.2. Use it for configuration fixes, mod updates, or crash fixes that do not change the pack’s purpose.

    Pre-release versions

    Section titled “Pre-release versions”

    A suffix marks a release before the final version:

    • 1.0.0-alpha.1: early experiment with major changes expected;
    • 1.0.0-beta.2: functional but still being validated;
    • 1.0.0-rc.1: release candidate.

    The final 1.0.0 release comes after its alpha, beta, and RC variants.

    For players

    Section titled “For players”

    Read the changelog before updating. A MAJOR change deserves special attention to worlds and servers. Back up even for smaller releases when world-generation mods change.

    For modpack creators

    Section titled “For modpack creators”

    Use PATCH for fixes, MINOR for compatible new content, and MAJOR when an update requires a new world, loses important compatibility, or changes the experience incompatibly. Never reuse a published version number for different content.

    Quick rules in Tegra

    Section titled “Quick rules in Tegra”
    1. Always enter all three numbers: 8.0.0, not just 8.0.
    2. Do not use a v prefix in the field: enter 8.0.1, not v8.0.1.
    3. Do not reuse a version already published on the same modpack line.

    Next steps

    Section titled “Next steps”

    This article adapts SemVer for Tegra. Read the official specification for build metadata, precedence, and every SemVer 2.0.0 rule. When publishing an update, return to the project workflow on the website and use the type of the largest included change.