Skip to content

docs: describe how the package actually releases #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
alihesari merged 1 commit into from
Oct 18, 2026
Merged

docs: describe how the package actually releases #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions CLAUDE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -199,8 +199,8 @@ on PRs, and on manual dispatch.

## Releasing

**`com.fopost:fopost-java` is NOT yet on Maven Central.** `.github/workflows/release.yml` exists
and is ready: it triggers on a `v*` tag (or manual dispatch), runs in the `central` GitHub
**`com.fopost:fopost-java` is on Maven Central** (0.2.0 at the time of writing).
`.github/workflows/release.yml` triggers on a `v*` tag (or manual dispatch), runs in the `central` GitHub
environment, verifies the tag matches `pom.xml` **and** that `Version.java` matches, runs
`mvn -B verify`, then publishes with `mvn -B -Prelease deploy -DskipTests` through the
`central-publishing-maven-plugin` (`autoPublish=true`) with GPG signing.
Expand All @@ -212,10 +212,10 @@ environment, verifies the tag matches `pom.xml` **and** that `Version.java` matc
- `GPG_PRIVATE_KEY`
- `GPG_PASSPHRASE`

First publish also requires, outside GitHub:
Publishing also depends on, outside GitHub:

1. **Namespace verification for `com.fopost`** on the Sonatype Central Portal (a DNS TXT record on
`fopost.com`). Nothing can be published until it is verified.
`fopost.com`). It is verified.
2. A **user token** generated on the Central Portal — that pair is what
`MAVEN_CENTRAL_USERNAME` / `MAVEN_CENTRAL_TOKEN` hold, not the portal login.
3. A **GPG key pair** whose public key is published to a public keyserver; the ASCII-armoured
Expand Down
Loading