Maven Releases
Repository
repositories {
maven { url = "https://astronomy20.github.io/MultiLib/maven/" }
}
Rebuilt on every push to 1.21.1, not just on CurseForge/Modrinth releases — the Maven coordinate tracks the latest commit; player-facing releases stay their own, less frequent milestones.
Coordinates
| Group | net.astronomy.multilib |
| Artifact | multilib |
See the Maven Version Index for every version published.
Versions
Every push publishes up to three version strings for the same content, so a version number is never silently overwritten with different bytes under the same name:
| Version | Meaning |
|---|---|
1.1.0-SNAPSHOT |
Always the latest push to 1.21.1. Mutable by Maven convention — Gradle re-checks it instead of caching it forever, unlike a bare release. Use this to track development without waiting for a release. |
1.1.0-<build number> |
A new, immutable version every push (MULTILIB_BUILD_NUMBER = the CI run number). Pin this for a reproducible build tied to one exact push. |
1.1.0 |
A real release — published once, the first time that mod_version is seen, then never touched again. |
Dependency
Embed via jarJar (NeoForge's jar-in-jar) when MultiLib is a fundamental, non-optional dependency, so players don't need to install it separately. jarJar.ranged(it, ...) is from an older ModDevGradle version and no longer exists on current versions (this project builds with net.neoforged.moddev 2.0.115) — use the current syntax instead, per the official docs. Tracking development (-SNAPSHOT):
dependencies {
jarJar(implementation("net.astronomy.multilib:multilib")) {
version {
strictly '[1.1.0-SNAPSHOT,)'
prefer '1.1.0-SNAPSHOT'
}
}
}
Pinning a release instead, once one exists:
dependencies {
jarJar(implementation("net.astronomy.multilib:multilib")) {
version {
strictly '[1.1.0,)'
prefer '1.1.0'
}
}
}
For an optional dependency, use a plain implementation(...) instead of jarJar(...), and declare it in neoforge.mods.toml.