Skip to content

Add a Maven-only release workflow - #4

Merged
SkyBlade1978 merged 1 commit into
MinecraftModDevelopmentMods:master-1.10.2from
SkyBlade1978:feature/maven-only-release
Nov 5, 2026
Merged

SkyBlade1978 merged 1 commit into
MinecraftModDevelopmentMods:master-1.10.2from
SkyBlade1978:feature/maven-only-release

Conversation

@SkyBlade1978

Copy link
Copy Markdown
Collaborator

The first 1.10.2 and 1.12.2 releases went to CurseForge, but the release tags did not upload them to MMD Maven. This adds a manual Maven-only workflow so I can backfill those releases without changing their versions or uploading them to CurseForge again.

It uses the existing CI main, sources and Javadoc jars. The main jar must match the public CurseForge download exactly. Check-only runs without upload credentials, and publication refuses a partially populated coordinate or different bytes at an existing coordinate.

I tested both versions in a disposable local Maven repository and checked the missing, identical, conflicting and partial destination cases.

@SkyBlade1978
SkyBlade1978 merged commit f5d75cb into MinecraftModDevelopmentMods:master-1.10.2 Nov 5, 2026
4 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