docs: fix stale llama-langchain4j README version + dedup README dependency snippets#296
Merged
Merged
Conversation
The 5.0.4 -> 5.0.5 release (PR #295) bumped the root README but missed llama-langchain4j/README.md, which still pointed consumers at 5.0.4. Root cause: the CLAUDE.md 'Version bump' section only said 'the README version examples and badge still need the usual manual update' without enumerating that there are TWO README files, so the module one was forgotten. Changes: - llama-langchain4j/README.md: 5.0.4 -> 5.0.5 (the stale snippet). - README.md: collapse the ~18 per-classifier <dependency> snippets into one canonical default snippet + one <classifier> template. The backend, target platform and runtime requirement already live once in the classifier table above, so the snippets were pure duplication. The release version now appears in ~4 spots instead of ~20. - CLAUDE.md: 'Version bump' section now enumerates BOTH README files that carry hardcoded release-version snippets (and notes the badge auto-pulls and the -SNAPSHOT line tracks the next dev version), so a future release cannot silently miss the module README again. No pom version is changed here; this branch is documentation + README consistency only, on top of the merged 5.0.5 release. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RXWwtbpTWjesgJdBWS27GJ
bernardladenthin
had a problem deploying
to
startgate
GitHub Actions
Error
|
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
2 participants
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.
Summary
llama-langchain4j/README.mdstill advertised<version>5.0.4</version>while the rest ofmainmoved to5.0.5. Bumped it to5.0.5.CLAUDE.md"Version bump" section only said "the README version examples and badge still need the usual manual update" without enumerating that there are two README files carrying hardcoded version snippets — which is why the module README was forgotten. It now lists both (README.md+llama-langchain4j/README.md), notes the Maven Central badge auto-pulls, and that the-SNAPSHOTline tracks the next dev version.<dependency>snippets into one canonical default snippet + one<classifier>template. The backend, target platform and runtime requirement already live once in the classifier table above, so the snippets were pure duplication. The release version now appears in ~4 spots instead of ~20 (−125 lines).No pom/version is changed here — the
5.0.5poms from #295 are already correct onmain. This is documentation + README consistency only.Test plan
CLAUDE.mdrelease checklist updatedmvn validateon the full reactor passes; all remaining version refs are5.0.5(plus the intentional5.0.5-SNAPSHOTsnapshot-channel line)Related issues / PRs
Checklist
🤖 Generated with Claude Code
Generated by Claude Code