release

name	release
description	Use when releasing RoutePeek to Maven Central or preparing a GitHub release.

RoutePeek Release

Preflight

1. Read gradle/libs.versions.toml and confirm libs.versions.routepeek is the intended release version.
2. Confirm both artifacts use the same version:
   • io.github.easyhooon:routepeek
   • io.github.easyhooon:routepeek-noop
3. Check Maven Central for existing immutable coordinates before publishing:
   • https://repo1.maven.org/maven2/io/github/easyhooon/routepeek/<version>/routepeek-<version>.pom
   • https://repo1.maven.org/maven2/io/github/easyhooon/routepeek-noop/<version>/routepeek-noop-<version>.pom
4. Ensure Gradle properties contain Maven Central and signing credentials, without printing secret values.

Verification

Run:

./gradlew :app:assembleDebug build
./gradlew publishToMavenLocal

Publish

Run ./gradlew clean before the actual upload to avoid stale artifacts.

For manual Maven Central publishing, use the Vanniktech tasks generated by this project:

./gradlew clean :routepeek:publishAndReleaseToMavenCentral :routepeek-noop:publishAndReleaseToMavenCentral

If the user wants upload without immediate release, use the corresponding publishToMavenCentral tasks and report the deployment state.

GitHub Release

1. Find the previous tag with gh release list --limit 3.
2. Review commits since the previous tag with git log --oneline <previous_tag>..HEAD.
3. Create an English release note matching the existing repo style.
4. Run gh release create <version> --title "<version>" --notes "<notes>".

Report

Report Maven Central task results, release URL, version, and published artifact coordinates.