pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: sehrope (@sehrope) <[email protected]>
To: pgjdbc/pgjdbc <[email protected]>
Subject: Re: [pgjdbc/pgjdbc] issue #3812: Release is releasing a SNAPSHOT version
Date: Fri, 19 Sep 2025 13:04:37 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
I don't consider it fixed until I see a release done end-to-end without any manual intervention with the action successful. The CI shows failure so that clearly has not happened yet.
And it sounds like we either need to backpatch whatever was fixed to the older branches. Or update how things run so that it uses the latest version of the workflow in master but publishes from a version built from a separate branch. That feels like it'd have less maintenance in the future (only worry about keeping it in sync in master) but I'm not sure if we'd need any special handling for publishing back-patch releases.
Are you going to back patch the release fixes?
When this is all settled, I actually want to run the whole thing again end to end. We don't have to wait for any meaningful code changes. Version numbers are cheap so we can burn as many as we want to ensure this thing is working.
view thread (5+ 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] issue #3812: Release is releasing a SNAPSHOT version
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