[BUG] 6.0.1370+ use the wrong Registrate version #106
Labels
No labels
Area-Assets
Area-Backend
Area-Conduits
Area-Datapacks
Area-Lang
Area-Mod Compat
Area-Parity
Area-Rendering
Good first issue
MC-1.19.2
MC-1.20.1
MC-1.20.4
MC-1.20.6
MC-1.21
MC-1.21.1
Modtoberfest
P-0-High
P-1-Medium
P-2-Low
Status-Awaiting Response
Status-Behind-Flag
Status-Blocked
Status-Cannot Reproduce
Status-Duplicate
Status-Help Wanted
Status-Incomplete Report
Status-Invalid
Status-Needs LTS Backport
Status-Needs Updating
Status-Stale
Status-To Implement
Status-Triage
Status-Wontfix
Status-Wontmerge
Type-Backport
Type-Bug
Type-Documentation
Type-Enhancement
Type-Question
Type-RFC
Type-Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Team-EnderIO/EnderIO#106
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
"EnderIO-6.0.1370/1371-alpha-nightly-all.jar" is suitable for 1.19.2,
but built-in "Registrate-MC1.19.3-1.1.10.jar",
instead of "Registrate-MC1.19-1.1.5.jar".
This has led to the following errors:
The following files can work properly:
Or only EnderIO-6.0.1369-alpha-nightly-all.jar
What are you trying to do, these are dev builds an aren't Available for Testing, and if you have issue, we can't help you sorry
Is it necessary to add an upper bound to "registrate_version_range"?
399e6cf881/gradle.properties (L35)I'm aware of this problem
the build jar is not intended for use yet
there should be an upper bound, but there was no good way to figure out what it should be, before the verwion released
this is also fixed already in one of my branches, will be fixed when that branch is merged