docs: document first fork pre-release - #36
Merged
Conversation
Publishing 0.4.3-fork.1 made eight sentences in the two READMEs false at once: four saying no release or tag existed, and four saying packaging one had not been decided. A ninth, not listed when the release went out but false from the same moment, said building from source was the only way to run this fork — which contradicted the paragraph four lines above it. Getting started now offers the two paths it should: download the archive attached to the pre-release, or clone this repository and build the same archive. The prerequisites are not duplicated; the upstream Usage section below already carries them. The pre-release is named as a pre-release wherever it appears, and said to be published to widen validation rather than because the work is finished. Nothing is described as stable or production ready. The upstream badges keep their upstream labels and their notes now name this fork's pre-release instead of denying it exists. The four remaining links to upstream's releases stay, each labelled as upstream's and each pointing the reader at this fork's own archive instead. Current status, Limitations, the test counts and the field record are untouched: nothing about them changed when the release was published. Documentation only. No code, no test, no workflow, no POM, no tag, no release modified. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Documentation only, aligning the two READMEs with the publication of
0.4.3-fork.1.What was false
Publishing the pre-release made eight sentences untrue at once — four saying no release or tag existed for this fork, four saying packaging one had not been decided.
A ninth, not listed when the release went out but false from the same moment: "Building from source is the only way to run this fork today." It contradicted the paragraph four lines above it, so it is corrected here too.
Each change answers the same question: was this sentence true before
0.4.3-fork.1was published, and false after? Nothing else was touched.Getting started
Two paths, in both languages:
studio-web-ui-0.4.3-fork.1-dist.zip, unzip, run the launcher for your platform. Prerequisites are not duplicated: the upstream Usage section below already carries them.mvn clean install, unchanged, now noted as producing the same archive.The pre-release is named as a pre-release everywhere it appears, and described as published to widen validation rather than because the work is finished.
Links
The two upstream badges keep their upstream labels; their notes now name this fork's pre-release instead of denying one exists. No new badge was added — a link was enough.
The four remaining links to upstream's releases stay in place, each labelled as upstream's build and each pointing the reader at this fork's own archive instead. No upstream link is presented as a download of this fork.
Verified rather than assumed: the release page returns 200, the asset is
uploadedat 20 565 684 bytes, and its download URL returns 200.Left alone
Current status, Limitations, the test counts (282 Java, 57 JavaScript) and the field record did not change when the release was published, so they are untouched — zero lines of them appear in the diff. Attribution to
marian-m12l/studiois unchanged, six occurrences per file. Nothing is described as stable or production ready.No code, no test, no workflow, no POM, no
TESTING.md, noFIELD-VALIDATION.md. No tag created or modified, no release modified.🤖 Generated with Claude Code