kzstd publishes org.meshtastic:kzstd to Maven Central with the vanniktech
maven-publish plugin, from .github/workflows/release.yml. JitPack
(com.github.meshtastic:kzstd) is a fallback channel.
SIGNING_KEY (the in-memory GPG key), OSSRH_USERNAME and OSSRH_PASSWORD (Central
Portal credentials), passed as the vanniktech ORG_GRADLE_PROJECT_* properties.
- Pick
X.Y.Z(SemVer; before 1.0 a minor may break). - On a branch, set
VERSIONandVERSION_NAMEingradle.propertiestoX.Y.Z, and runscripts/changelog.sh cut X.Y.Z. That moves## [Unreleased]under a dated## [X.Y.Z]heading and updates the compare links, touching nothing else. It refuses an empty Unreleased. - If the public API changed,
./gradlew apiDumpand commitapi/. - Commit
chore(release): X.Y.Z(signed off), open the PR and merge it. gh workflow run release.yml --repo meshtastic/kzstd -f version=X.Y.Z. Add-f dry_run=trueto run every gate without tagging or publishing; a dry run may start from any branch. Pushing avX.Y.Ztag onmainruns the same workflow.
- The commit is on
main(skipped for a dry run). - The version equals
VERSIONandVERSION_NAME, and any existingvX.Y.Ztag points at this commit. scripts/changelog.sh notes X.Y.Zfinds a non-empty section. It becomes the GitHub Release body verbatim.- Every check the
mainruleset requires passed on this commit (scripts/release-checks.sh green-ci). That is where the Apple tests ran; this Linux runner cannot run them. ./gradlew build, thenpublishToMavenLocalwith signing.- No staged POM or Gradle module depends on a
-SNAPSHOT(scripts/release-checks.sh no-snapshots). Central rejects that only after upload. - If
X.Y.Zis already onrepo1.maven.orgthe publish is skipped, so a re-run is safe.
Then it attests every staged artifact, pushes the annotated vX.Y.Z tag if it is
missing, runs publishAndReleaseToMavenCentral, and creates or updates the GitHub
Release.
repo1.maven.org lags the Central Portal by 10 to 30 minutes. Downstream bumps wait
until https://repo1.maven.org/maven2/org/meshtastic/kzstd-jvm/X.Y.Z/ resolves.