Message-ID: <gh-pgjdbc-pgjdbc-4079-c4507845079@github.com>
From: "vlsi (@vlsi)" <noreply+vlsi@github.com>
To: "pgjdbc/pgjdbc" <noreply+pgjdbc-pgjdbc@github.com>
Date: Thu, 21 May 2026 11:40:43 +0000
Subject: Re: [pgjdbc/pgjdbc] PR #4079: docs: spell out the proactive-security window in SECURITY.md
In-Reply-To: <gh-pgjdbc-pgjdbc-4079@github.com>
References: <gh-pgjdbc-pgjdbc-4079@github.com>
List-Id: <gh-pgjdbc-pgjdbc.github.com>
X-GitHub-Author-Login: vlsi
X-GitHub-Comment-Id: 4507845079
X-GitHub-Comment-Type: issue_comment
X-GitHub-Issue: 4079
X-GitHub-Repo: pgjdbc/pgjdbc
X-GitHub-Type: comment
X-GitHub-Url: https://github.com/pgjdbc/pgjdbc/pull/4079#issuecomment-4507845079
Content-Type: text/plain; charset=utf-8

Technically, the all the 42.x branches use Gradle, even 42.2.x
Sure there might be issues. However, let's see if the issues are real first.

For example, Sonatype released a compatibility endpoint: https://central.sonatype.org/publish/publish-portal-ossrh-staging-api/#getting-started-for-maven-api-like-plugins, so even old build systems should be able to publish to Central after reconfiguring the oss.sonatype.org link to the compatibility URL.