1.2.1-ALPHA.5
Compatibility
Changes
v1.2.1
This pull request removes the beta branch workflow, updates the main branch workflow, increments the plugin version, updates platform dependencies, and removes the libs.versions.toml file. These changes streamline the project configuration and focus on maintaining the main branch release process.
Workflow Changes:
- Removed the beta branch workflow, including steps for publishing to GitHub Packages, Hangar, and Modrinth.
- Updated the workflow name to "Release & Publish Packages (Main Branch)" to reflect the focus on the main branch.
Version Updates:
- Incremented
pluginVersionfrom1.2.0to1.2.1and updatedpaperVersionfrom1.21.7to1.21.8.
Dependency Configuration:
- Removed the dependency version management file, simplifying the project configuration.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:Ksss1YfG:N1kJWbsS"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Ksss1YfG:N1kJWbsS"
}

