[pgjdbc/pgjdbc] PR #3686: chore: migrate publish workflow to Central Portal publishing via com.gradleup.nmcp

pgjdbc/pgjdbc GitHub issues and pull requests (mirror)  
help / color / mirror / Atom feed

From: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: [pgjdbc/pgjdbc] PR #3686: chore: migrate publish workflow to Central Portal publishing via com.gradleup.nmcp
Date: Tue, 24 Jun 2025 18:50:00 +0000
Message-ID: <[email protected]> (raw)

The idea is to use GitHub Actions for releasing pgjdbc.

[Central Portal is a requirement](https://central.sonatype.org/news/20250326_ossrh_sunset/) to publish since 30 June, so we need to migrate the workflow.

The suggested flow is as follows:
1. Prepare release notes, commit it to Git.
2. Open the "release" action at 👉 [Actions tab → release.yml](https://github.com/pgjdbc/pgjdbc/actions/workflows/release.yml).
3. Click "run workflow".
4. Set "Release version number" if you want to bump the version before the release. Note: if the current version already exists, then the release workflow would abort.
5. Click "Run workflow"

Open items:
* [ ] Decide which PGP will be used to sign releases. In theory, we can create a new "pgjdbc/pgjdbc signing key"
* [ ] Decide if we want updating the site as a part of the release job
* [ ] Add GitHub App for `actions/create-github-app-token` (see [usage](https://github.com/actions/create-github-app-token?tab=readme-ov-file#usage)) so it could get app tokens for "bump version" commits
* [ ] Test release workflow. I plan testing the workflow in `vlsi/pgjdbc` fork to ensure branch names, and the workflow steps are good for pgjdbc.

view thread (3+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: github://pgjdbc/pgjdbc
  Cc: [email protected], [email protected]
  Subject: Re: [pgjdbc/pgjdbc] PR #3686: chore: migrate publish workflow to Central Portal publishing via com.gradleup.nmcp
  In-Reply-To: <<[email protected]>>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox