Uh oh!
There was an error while loading. Please reload this page.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🧩 Analysis chain
🏁 Script executed:
Repository: Lightprotocol/light-protocol
Length of output: 224
🏁 Script executed:
Repository: Lightprotocol/light-protocol
Length of output: 1895
Fix the chronological ordering of PRs across client and photon-api changelogs.
PRs
#2219and#2198appear insdk-libs/client/CHANGELOG.mdunder[0.21.0](2026-02-10) and again insdk-libs/photon-api/CHANGELOG.mdunder[0.55.0](2026-02-17). This is backwards: the client claims to have added "compressed mint support via photon API" on 2026-02-10, but the API itself didn't add that feature until 2026-02-17. Similarly, the client replaced the photon-api client on 2026-02-10, but photon-api replaced its own implementation on 2026-02-17.Either the CHANGELOG dates are incorrect, or the PR assignments are wrong. Verify that the dates correspond to actual release points and that PR associations reflect when they were actually merged for each package.
🤖 Prompt for AI Agents