Releases: stromblex/Kernova
Release list
Kernova tooling 0.1.8-beta
Summary
- Split publish packaging and changelog handling by platform so Modrinth and CurseForge can use platform-specific release notes and artifacts.
- Added platform selection for packaging and PackPing sync paths.
- Improved upload/release flow so a successful platform can continue when the other platform fails during a combined release.
- Updated publish tests for the new partial-success release behavior.
Validation
updater/.venv/bin/python -m unittest discover -s updater/testsupdater/.venv/bin/kernova-update validate --artifactspython3 publish/publish.py upload --latest --loader both --mc 26.1.2 --platform both --dry-run
Publishing
- Modrinth and CurseForge modpack uploads were not performed.
- PackPing feed sync/push was not performed.
- No remaining manual work is known.
Kernova tooling 0.1.7-beta
Kernova tooling 0.1.7-beta
Changes:
- Fixed Modrinth version numbers so releases for different Minecraft versions no longer collide when pack versions match.
- Reworked PackPing feed generation to preserve the latest build version for each Minecraft/loader line without downgrading entries during packaging.
- Made PackPing changelogs short and generic for in-game display.
- Changed PackPing download URLs to project homepages for Modrinth and CurseForge upgrade notices.
- Added regression tests for Modrinth version numbering, PackPing Minecraft-upgrade notices, homepage links, and same-Minecraft downgrade prevention.
Validation:
updater/.venv/bin/python -m unittest discover -s updater/testsupdater/.venv/bin/kernova-update validate --artifactspython3 publish/publish.py upload --latest --loader both --mc 26.1.1 --platform both --dry-runpython3 -m json.tool publish/config.json
Not performed:
- No Modrinth or CurseForge modpack uploads were performed.
- No PackPing feed sync or push was performed as part of this tooling release.
Remaining manual work:
- PackPing itself still needs a code update if toast-only notices should display when the local pack version is already equal to the feed entry version.
Kernova tooling 0.1.6-beta
Kernova tooling 0.1.6-beta
Tooling changes:
- Added changelog generation that compares rebuilds with the previous matching manifest and avoids duplicating generated sections from manual notes.
- Hardened CurseForge upload metadata by rejecting invalid environment IDs.
- Made Modrinth uploads idempotent when the target version already exists.
- Improved VartaPack Doctor launching with Java override support, runtime diagnostics, and a vendored Gson dependency.
Validation:
updater/.venv/bin/python -m unittest discover -s updater/testsupdater/.venv/bin/kernova-update validate --artifacts- Publish upload dry-run skipped because no Modrinth
.mrpackor CurseForge.zipartifacts are present underpublish/.
Modpack publishing was intentionally not performed, and the PackPing public feed was not pushed.
Remaining manual work:
- None for the tooling release.
Kernova tooling 0.1.5-beta
Kernova tooling 0.1.5-beta
Tooling-only beta release for the Kernova publish/update automation.
Changes
- Split PackPing feed handling into platform-specific Modrinth and CurseForge update files, remote filenames, update URLs, and download URL templates.
- Inject the correct platform-specific PackPing
updateUrlinto packaged configs for Modrinth, CurseForge, full, and Prism artifacts. - Generate concise PackPing feed changelog entries and support blank or empty PackPing feed JSON files during validation.
- Add Modrinth project side metadata sync for
client_sideandserver_side, including dry-run reporting. - Expand publish channel handling to include
alphaand reject invalid configured release types. - Update CurseForge game version metadata with the configured environment id and add tests for packaging, upload, sync, and validation paths.
Validation
updater/.venv/bin/python -m unittest discover -s updater/testsupdater/.venv/bin/kernova-update validate --artifactspython3 publish/publish.py upload --latest --loader both --mc 26.1 --platform both --dry-run
Publishing Scope
No Modrinth or CurseForge modpack artifacts were uploaded.
The PackPing public feed was not synced or pushed.
Remaining Manual Work
None.
Kernova tooling 0.1.4-beta
Kernova tooling 0.1.4-beta
- Changed Modrinth
version_typeand CurseForgerelease_typeconfig toauto. - Added publisher logic that derives release, beta, or alpha from the pack
pack_versionsuffix, falling back to release for unknown or unsuffixed versions. - Covered automatic release-channel metadata for CurseForge and Modrinth upload paths with unit tests.
Validation:
updater/.venv/bin/python -m unittest discover -s updater/testsupdater/.venv/bin/kernova-update validate --artifacts- Modpack upload dry-run skipped because no
.mrpackor.zipartifacts exist in the working tree.
Modpack publishing was intentionally not performed. PackPing feed was not pushed.
Remaining manual work: none.
Kernova tooling 0.1.3-beta
Kernova tooling 0.1.3-beta
Tooling-only beta release for the Kernova publish and validation pipeline.
Changes
- Added CurseForge file fingerprint resolution so generated CurseForge modpack manifests reference project/file IDs instead of embedding resolved mod jars under overrides.
- Added support for configured CurseForge file overrides when a mod jar should be mapped without calling the fingerprint API.
- Added CurseForge
modlist.htmlgeneration and safer publish error handling for manifest packaging failures. - Tightened artifact validation to reject CurseForge zips with missing file references or embedded mod jars.
- Expanded updater tests for CurseForge packaging, unmatched jar failures, configured file overrides, and artifact validation.
Validation
updater/.venv/bin/python -m unittest discover -s updater/testspassed: 35 tests.updater/.venv/bin/kernova-update validate --artifactspassed with 0 errors and 3 expected warnings because no publish artifacts/feed output are present.- Upload dry-run was skipped because there are no generated Modrinth/CurseForge artifacts to dry-run.
Publishing
- No Modrinth or CurseForge modpack artifacts were uploaded.
- PackPing feed was not pushed.
- No remaining manual work for this tooling release.
Kernova tooling 0.1.2-beta
Kernova tooling 0.1.2-beta
Changes
- Added CurseForge-specific modpack zip generation with a
manifest.jsonandoverrides/layout, replacing the previous full-overrides zip upload artifact path. - Updated CurseForge artifact selection and package output naming to use
publish/curseforge/**/*-curseforge.zip. - Added validation for CurseForge modpack zips, including manifest type/version, Minecraft version, mod loader metadata, and overrides folder presence.
- Split real release uploads for
--platform bothso Modrinth and CurseForge uploads are handled explicitly after the dry-run gate. - Removed the now-unused
allow_full_overrides_zippublishing config flag.
Validation
updater/.venv/bin/python -m unittest discover -s updater/testspassed: 32 tests.updater/.venv/bin/kernova-update validate --artifactspassed with 0 errors and 4 expected missing-artifact warnings.- Platform upload dry-run was skipped because no build/modpack artifacts exist in this checkout.
Publishing
- Modrinth and CurseForge modpack artifacts were intentionally not uploaded for this tooling-only release.
- The PackPing public feed was intentionally not synced or pushed.
Remaining Manual Work
- None.
Kernova tooling 0.1.1-beta
Kernova tooling 0.1.1-beta
This tooling beta fixes NeoForge .mrpack dependency resolution so modern Minecraft versions resolve against the exact NeoForge patch branch instead of drifting to a newer incompatible branch.
Changes:
- Added exact NeoForge Maven prefix handling for both legacy
1.xand modern26.xMinecraft versions. - Pinned known NeoForge loader versions for
26.1,26.1.1, and26.1.2. - Added artifact validation that rejects NeoForge
.mrpackfiles whose dependency does not match the Minecraft patch branch. - Added unit coverage for NeoForge dependency selection and artifact validation.
- Bumped the updater package metadata to
0.1.1b0.
Validation:
updater/.venv/bin/python -m unittest discover -s updater/testspassed.updater/.venv/bin/kernova-update validate --artifactspassed with 0 errors and 3 expected warnings because no generated builds, Modrinth artifacts, or PackPing update JSON are present in this checkout.python3 publish/publish.py upload --latest --loader both --mc 26.1 --platform both --dry-runwas not completed because no matchingbuild_manifest.jsonexists inbuilds/.
Modpack publishing was intentionally not performed for this tooling-only release.
PackPing feed publishing was intentionally not performed.
Kernova tooling 0.1.0-beta
Kernova tooling 0.1.0-beta
First beta milestone for the Kernova automation repository. This release is for tooling and source automation, not a modpack artifact upload.
Highlights
- Modrinth-only mod resolution and dependency-aware build support for Fabric and NeoForge profiles.
- CurseForge publishing flow supports full-zip upload artifacts with dry-run metadata checks.
- Release flow can sync and push the PackPing update feed automatically.
- PackPing feed notices can show Minecraft-upgrade toast messages.
- VartaPack support generates profile, rules, support config, integrity manifests, and Doctor-mode checks.
- Validation and unittest coverage now cover repository layout, builder behavior, versioning, publishing, and validation paths.
Validation
- Source validation passed with 0 errors and 0 warnings.
- Artifact validation reported 0 errors and expected warnings for absent generated builds/artifacts in this tooling-only checkout.
- Unit tests passed: 26 tests.
- Generated modpack artifacts are intentionally not attached to this release.