Skip to content

fix: require a digit in loader versions - #21

Merged
NeyorDEV merged 1 commit into
mainfrom
fix/loader-version-needs-digit
Oct 20, 2026
Merged

NeyorDEV merged 1 commit into
mainfrom
fix/loader-version-needs-digit

Conversation

@NeyorDEV

Copy link
Copy Markdown
Owner

Follow-up to #20, found during a real run.

Problem

migrate --loader-version X.Y.Z, a placeholder copied from an example, was accepted because it has the form of a version. ModShift then wrote a .mrpack that launchers can't use.

Fix

Every real loader version contains a digit, so a value without one (X.Y.Z, latest) is now rejected before any request is sent.

The check applies to --loader-version, target.loaderVersion and the web UI. Tests and CHANGELOG are updated.

Checks

lint, format, typecheck, build and the docs diff are clean. 440 tests pass.


Generated by Claude Code

A real run accepted "--loader-version X.Y.Z" (another placeholder copied
from an example) because it looks like a version, and wrote an unusable
pack. Every real loader version contains a digit, so values without one
(X.Y.Z, latest) are now rejected before any request.
@NeyorDEV
NeyorDEV merged commit 9b68de1 into main Oct 20, 2026
2 checks passed
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.

1 participant