Repository navigation
docs: pair codec-java 0.6.0 with the 0.5.x server line - #503
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 (1M context) <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
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
I'm getting ready to release
0.5.0and the compatibility table has no row for it. It stops at codec-java0.3.0against the0.4.xserver.The pairing is unambiguous from the trees.
v0.4.7carries codec-java at0.3.0-SNAPSHOT, so the existing0.3.0row is right. Every codec-java release since —0.4.0,0.5.0,0.6.0— was cut from a tree where the server read0.5.0-SNAPSHOT, so they all belong to the0.5.xline, and0.6.0is the latest of them.mainis on0.7.0-SNAPSHOTnow, which is the next line's row to write when it ships.Changes
0.6.0 | 0.5.xto the compatibility table inRELEASES.md.How to Test
Read the table. Nothing builds from it.
AI Assistance