You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit ae37fbf
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CLAUDE.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -72,5 +72,6 @@ Each `Router<C>` wraps a Decompose `*Navigation<C>` (delegating navigation calls
72
72
## Versioning & publishing
73
73
74
74
- Versions are centralized in `gradle/libs.versions.toml`. Current version is set in the root `build.gradle.kts` (`allprojects { version = ... }`).
75
-
- Publishing targets Sonatype Central Portal. `SNAPSHOT` versions go to the snapshots repo; releases to the staging deploy API. Credentials (`sonatypeUsername`/`sonatypePassword`, `gpgKeySecret`/`gpgKeyPassword`) are read from `local.properties` (git-ignored; CI writes them from secrets). Artifacts are GPG-signed and ship a Dokka-generated `javadocJar`.
76
-
- CI (`.github/workflows/build.yml`) runs `apiCheck` → per-target tests + Android emulator tests → (on push to `main`) release to Sonatype and publish docs to GitHub Pages.
75
+
- Publishing uses the `com.vanniktech.maven.publish` plugin, applied to every published subproject from the root `build.gradle.kts``subprojects {}` block (the `app` is skipped). Two registries: Maven Central via `publishToMavenCentral` (Sonatype Central Portal, `SNAPSHOT`s go to the snapshots repo; releases wait for manual "Publish" on the portal since there's no `automaticRelease`) and GitHub Packages via `publishAllPublicationsToGitHubPackagesRepository`. Artifacts are GPG-signed (`signAllPublications()`) and the plugin wires the Dokka javadoc jar automatically.
76
+
- Credentials are Gradle properties, not `local.properties`: `mavenCentralUsername`/`mavenCentralPassword` and `signingInMemoryKey`/`signingInMemoryKeyPassword` for Central; `GITHUB_ACTOR`/`GITHUB_TOKEN` env vars for GitHub Packages. In CI these come from `ORG_GRADLE_PROJECT_*` env vars fed by repo secrets (`MAVEN_CENTRAL_USERNAME`/`MAVEN_CENTRAL_PASSWORD`, `GPG_KEY_SECRET`/`GPG_KEY_PASSWORD`).
77
+
- CI (`.github/workflows/build.yml`) runs `apiCheck` → per-target tests + Android emulator tests → (on push to `main`) a `release` matrix job publishing to both registries and a docs job publishing to GitHub Pages.
0 commit comments