1.3.2-ALPHA.23
Compatibility
Changes
v1.3.2
This pull request updates the GitHub Actions workflows for the Alpha, Beta, and Main branches to streamline the release and publishing processes. Key changes include renaming workflows for clarity, adding detailed comments, and expanding publishing steps to include GitHub Packages, Hangar, and Modrinth.
Workflow Updates for Release and Publishing
Renaming and Branch-Specific Updates:
- Renamed workflow to "Release & Publish Packages (Alpha Branch)" and added branch-specific publishing steps for the Alpha channel.
- Renamed workflow to "Release & Publish Packages (Beta Branch)" and added branch-specific publishing steps for the Beta channel.
- Renamed workflow to "Release & Publish Packages (Beta Branch)" and updated branch trigger from
maintobeta.
Expanded Publishing Steps:
- Added new steps to publish artifacts to GitHub Packages (Maven), Hangar, and Modrinth platforms across all workflows. Each step includes environment variable setup and detailed comments explaining their purpose.
Improved Documentation:
- Enhanced comments throughout the workflows to clarify the purpose of each step and the configuration details, such as Gradle wrapper validation, JDK setup, and publishing tasks. This pull request updates the GitHub Actions workflows for the Alpha, Beta, and Main branches to standardize and enhance the release and publishing process. Key changes include renaming workflows for clarity, adding detailed comments, and expanding publishing steps to support multiple platforms (GitHub Packages, Hangar, and Modrinth).
Workflow Enhancements:
-
Renamed workflow names for clarity:
- Changed name to "Release & Publish Packages (Alpha Branch)."
- Changed name to "Release & Publish Packages (Beta Branch)."
- Changed name to "Release & Publish Packages (Beta Branch)."
-
Expanded publishing steps to support GitHub Packages, Hangar, and Modrinth:
- Added publishing steps for Maven (
./gradlew publish), Hangar (./gradlew publishPluginPublicationToHangar), and Modrinth (./gradlew modrinth) with appropriate environment variables and comments for each workflow.
- Added publishing steps for Maven (
Documentation Improvements:
- Added comments to clarify workflow steps, such as checking out the repository, validating the Gradle wrapper, and setting up JDK 21. These changes improve readability and maintainability across all workflows.
Branch-Specific Adjustments:
- Updated the branch targeting in
.github/workflows/main.ymlto focus on the Beta branch instead of Main, aligning with the new workflow name and purpose.
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:q790UNpr:6d66I6BG"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:q790UNpr:6d66I6BG"
}

