pgjdbc/pgjdbc GitHub issues and pull requests (mirror)help / color / mirror / Atom feed
[pgjdbc/pgjdbc] PR #3701: chore: add GitHub Actions workflow for generating release PGP key 5+ messages / 3 participants [nested] [flat]
* [pgjdbc/pgjdbc] PR #3701: chore: add GitHub Actions workflow for generating release PGP key @ 2025-06-30 20:19 "vlsi (@vlsi)" <[email protected]> 0 siblings, 0 replies; 5+ messages in thread From: vlsi (@vlsi) @ 2025-06-30 20:19 UTC (permalink / raw) To: pgjdbc/pgjdbc <[email protected]> See https://github.com/vlsi/provision-release-pgp-key We can copy-paste the workflow right into pgjdbc repository or we can have it as reusable workflow. Any thoughts? See also: * https://slxh.nl/blog/2016/pgp-and-dns/ * https://www.netmeister.org/blog/dnssec-dane.html#dane ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3701: chore: add GitHub Actions workflow for generating release PGP key @ 2025-06-30 20:29 "davecramer (@davecramer)" <[email protected]> 3 siblings, 0 replies; 5+ messages in thread From: davecramer (@davecramer) @ 2025-06-30 20:29 UTC (permalink / raw) To: pgjdbc/pgjdbc <[email protected]> Just as easy to keep it as a re-usable workflow in the event that something changes in the future ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3701: chore: add GitHub Actions workflow for generating release PGP key @ 2025-07-01 10:34 "vlsi (@vlsi)" <[email protected]> 3 siblings, 0 replies; 5+ messages in thread From: vlsi (@vlsi) @ 2025-07-01 10:34 UTC (permalink / raw) To: pgjdbc/pgjdbc <[email protected]> I did not intend creating a new branch in pgjdbc/pgjdbc though. ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3701: chore: add GitHub Actions workflow for generating release PGP key @ 2025-07-01 10:35 "vlsi (@vlsi)" <[email protected]> 3 siblings, 0 replies; 5+ messages in thread From: vlsi (@vlsi) @ 2025-07-01 10:35 UTC (permalink / raw) To: pgjdbc/pgjdbc <[email protected]> I've updated the workflow so it explicitly passes the required secrets instead of passing all the secrets with `secrets:inherit`. Now the missing bit is to settle on the key name and the key email. ^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: [pgjdbc/pgjdbc] PR #3701: chore: add GitHub Actions workflow for generating release PGP key @ 2025-09-19 06:11 "dsvensson (@dsvensson)" <[email protected]> 3 siblings, 0 replies; 5+ messages in thread From: dsvensson (@dsvensson) @ 2025-09-19 06:11 UTC (permalink / raw) To: pgjdbc/pgjdbc <[email protected]> I guess this is the related to the key change to: https://keyserver.ubuntu.com/pks/lookup?search=305F296EAC47556B&fingerprint=on&op=index Would be very nice to have the release key recorded in git history for example here: https://github.com/pgjdbc/pgjdbc?tab=security-ov-file ^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~2025-09-19 06:11 UTC | newest] Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2025-06-30 20:19 [pgjdbc/pgjdbc] PR #3701: chore: add GitHub Actions workflow for generating release PGP key "vlsi (@vlsi)" <[email protected]> 2025-06-30 20:29 ` "davecramer (@davecramer)" <[email protected]> 2025-07-01 10:34 ` "vlsi (@vlsi)" <[email protected]> 2025-07-01 10:35 ` "vlsi (@vlsi)" <[email protected]> 2025-09-19 06:11 ` "dsvensson (@dsvensson)" <[email protected]>
This inbox is served by agora; see mirroring instructions for how to clone and mirror all data and code used for this inbox