pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: vlsi (@vlsi) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: [pgjdbc/pgjdbc] PR #3963: chore: use full version tags in GitHub Actions comments
Date: Sat, 14 Mar 2026 19:18:14 +0000
Message-ID: <[email protected]> (raw)
Replace branch-style version comments (e.g. # v4) with full tag names (e.g. # v4.3.1) for all action references. Also add missing version comment for codecov/codecov-action and update provision-release-pgp-key to v1.0.0.
Currently renovate updates look like `chore(deps): update release-drafter/release-drafter digest to 6a93d82` which is not human-readable. If we use tag names like `v4.3.1`, then renovate would create PRs like `bump to v4.3.1` rather than `bump to 6a93d82`
view thread (6+ 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 #3963: chore: use full version tags in GitHub Actions comments
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