pgjdbc/pgjdbc GitHub issues and pull requests (mirror)
help / color / mirror / Atom feedFrom: vlsi (@vlsi) <[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:47:09 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
Thanks, Sehrope!
I fully agree with you — the real goal here is to have a smooth, fully automated release that can run end-to-end without manual steps. The last run failed only due to a branch protection rule at the final stage; I’ve already adjusted the rule, so that specific problem won’t occur again in the next run.
That said, we did successfully roll out 42.7.8 to both Central and GitHub Releases, so from a user’s perspective the release is already out there. What’s still pending is updating [jdbc.postgresql.org](https://jdbc.postgresql.org/), otherwise users may get confused by the mismatch. I’d like to get that site updated before cutting the next release. Longer term, I think it would be great to automate the website deployment as part of the process.
On “back-patching”
The release workflow only exists on master right now, so there’s nothing to back-patch in older branches. We could certainly copy the workflow into older release branches if we want a consistent experience across them, but that’s a separate step from fixing the recent CI failure.
On burning versions
I’m fine with doing another end-to-end test release once the website is updated. We should just be mindful that every new tag triggers dependabot updates across a lot of projects, so it’s worth balancing the desire to test with the impact on downstream consumers.
So, in short:
* The branch-rule blocker is fixed.
* Next step: update jdbc.postgresql.org for 42.7.8.
* Then we can run the next release end-to-end with the updated workflow.
If you have extra issues, please feel free to open issues so we don't accidentally lose the items.
view thread (5+ messages)
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