You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Update the Maven Central publishing URL to avoid sunset service (#3457)
The service we were using to publish to Maven Central was sunset. There
is a legacy API that allows us to continue to use our old publising
gradle platform, and so I've updated the configuration so that it
follows the advice available on their website:
https://github.com/gradle-nexus/publish-plugin?tab=readme-ov-file#publishing-to-maven-central-via-sonatype-central
This is advertised to be pretty straightforward. The two main steps are
(1) update the publishing URL to one that uses a bridge API and (2)
modify the credentials to ones generated by the new portal. I've done
that (and already updated the secrets on the repo with the new
credentials). So we should be able to get a new build published through
the new gateway once this is in.
I've also gone ahead and removed the release notes for the builds that
never actually were published. That way, when we get a new build out,
we'll get the correct set of release notes automatically without needing
to tweaks those by hand later.
This fixes#3456.
Copy file name to clipboardExpand all lines: docs/sphinx/source/ReleaseNotes.md
-53Lines changed: 0 additions & 53 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,59 +5,6 @@ This document contains a log of changes to the FoundationDB Record Layer. It aim
5
5
6
6
As the [versioning guide](Versioning.md) details, it cannot always be determined solely by looking at the version numbers whether one Record Layer version contains all changes included in another. In particular, bug fixes and backwards-compatible changes might be back-ported to or introduced as patches against older versions. To track when a patch version has been included in the main release train, some releases will say as a note that they contain all changes from a specific patch.
[See full test run](https://github.com/FoundationDB/fdb-record-layer/actions/runs/16003773419)
23
-
24
-
25
-
26
-
### 4.4.1.0
27
-
28
-
<h4> New Features </h4>
29
-
30
-
* Improve MetaDataProtoEditor handling of unqualified types and add support for renaming all the types - [PR #3402](https://github.com/FoundationDB/fdb-record-layer/pull/3402)
31
-
* Enable the Planner Rewrite Rules - [PR #3401](https://github.com/FoundationDB/fdb-record-layer/pull/3401)
32
-
<h4> Bug Fixes </h4>
33
-
34
-
* add placeholders in all appropriate select expressions - [PR #3451](https://github.com/FoundationDB/fdb-record-layer/pull/3451)
35
-
36
-
<details>
37
-
<summary>
38
-
39
-
<h4> Build/Test/Documentation/Style Improvements (click to expand) </h4>
0 commit comments