Archive the BanyanDB Java Client - #899
Merged
Merged
Conversation
The client is deprecated: BanyanDB clients, including the OAP server, use the BanyanDB Client Proto directly, so there is nothing left to release here. - docs.yml: move it out of Database into Archived Repositories, as "(Archived) BanyanDB Java Client", dropping the README doc links so the card matches the other archived repositories. - releases.yml: move v0.9.1 into Archived Releases and repoint src/asc/sha512 at archive.apache.org, since downloads.apache.org only carries current releases and this component will not have another one. The Maven coordinates are unchanged. Also fixes the "Oct 15th , 2025" date to the "Mon. DDth, YYYY" form used everywhere else. This is also why the Archived Releases section looked broken. It was added as a bare "- type:" with no list, so the chip and the <h2> rendered but the grid below them was empty — the section existed with nothing in it. It now has its first entry. The card keeps its BanyanDBJavaClient id, so existing links to /downloads/#BanyanDBJavaClient still resolve.
❌ Deploy Preview for skywalking-website-preview failed.
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The BanyanDB Java Client is deprecated — BanyanDB clients, including the OAP server, use the BanyanDB Client Proto directly, so there is nothing further to release.
Changes
data/docs.yml— moved out of Database into Archived Repositories as(Archived) BanyanDB Java Client. The README doc links are dropped so the card matches the other archived repositories (bare card linking to the repo, no "Read docs →").data/releases.yml— moved v0.9.1 into Archived Releases, withsrc/asc/sha512repointed atarchive.apache.org.downloads.apache.orgonly carries current releases, and this component will not have another one; all three archive URLs verified 200. Maven coordinates unchanged. Also corrected theOct 15th , 2025date to theMon. DDth, YYYYform used everywhere else.Why the Archived Releases section looked broken
This is the second issue in the report.
- type: Archived Releaseswas added toreleases.ymlas a bare header with nolist:, and nothing was ever moved into it. The chip loop inlayouts/downloads/list.htmland the<h2>inlayouts/shortcodes/downloads-block.htmlboth render unconditionally, so the live page has been emitting:— a heading and a chip that jump to an empty grid, which reads as a missing section. It now has its first entry. (If you'd like a hard guard so a future empty category can't render a dead chip and heading again, that's a small change in those two templates — say the word and I'll add it.)
Verification
Local Hugo build, 5421 pages, no errors:
BanyanDBJavaClient, v0.9.1 source + distribution, 3 archive.apache.org linksBanyanDB Server (BanyanD),BanyanDB Command Line Tool (bydbctl),BanyanDB HelmBanyanDB,BanyanDB Client Proto,BanyanDB Helm(Archived) OAL Generator,(Archived) BanyanDB Java ClientThe card keeps its
BanyanDBJavaClientid, so existing links to/downloads/#BanyanDBJavaClientstill resolve — they now land in Archived Releases.Not done here
The GitHub repo itself still reports
archived=false. Flipping that flag is a separate action onapache/skywalking-banyandb-java-client.