lfreleng-actions/Central Publish Action
Publish Maven artifacts to Maven Central via the Central Portal REST API. Optionally signs artifacts with GPG (signing-method=gpg) or accepts artifacts pre-signed via sigul (signing-method=sigul), creates a bundle ZIP, uploads to Central Portal, and polls for deployment status.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 8, 2026
- License
- None
Pinned Snippet
uses: lfreleng-actions/central-publish-action@6af98d56275d1e4326567773533b8a0ccace6634 # v0.1.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| m2repo-path | Path to local Maven repository directory containing artifacts | yes | m2repo |
| central-username | Central Portal token username | yes | — |
| central-token | Central Portal token password | yes | — |
| signing-method | How artifacts are signed: 'gpg' (this action imports gpg-private-key and signs), 'sigul' (artifacts MUST be pre-signed by the caller, e.g. via lfit/sigul-sign-action, before this action runs — it only verifies the .asc files exist), or 'none' (no signing; for dry-run / non-Central use). | no | gpg |
| gpg-private-key | GPG private key (base64 encoded, armor format). Required only when signing-method is 'gpg'. | no | "" |
| gpg-passphrase | GPG key passphrase (empty if no passphrase) | no | "" |
| publishing-type | AUTOMATIC (auto-publish) or USER_MANAGED (validate only) | no | USER_MANAGED |
| dry-run | If true, create bundle but skip upload | no | false |
| poll-timeout | Max seconds to wait for deployment validation | no | 600 |
| poll-interval | Seconds between status polls | no | 15 |
Outputs
| name | description |
|---|---|
| deployment_id | Central Portal deployment ID |
| deployment_status | Final deployment status |
| bundle_path | Path to created bundle ZIP |