docs: release notes for February 2026 releases#27
docs: release notes for February 2026 releases#27klausundklaus wants to merge 2 commits intoLightprotocol:mainfrom
Conversation
WalkthroughChangelog updated with release entries for SDK v0.23.0, v0.22.1, v0.22.0, v0.21.0 and Devnet Program v2.2.0/v2.3.0, plus beta release notes, migration snippets, and deployment details. All edits are documentation-only. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~8 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
🧹 Nitpick comments (3)
changelog.mdx (3)
156-157: Missing description forlight-token-client.The
light-token-client v0.21.0entry lacks a description, unlike the other crates in this section. Consider adding a brief note about what changed, or explicitly marking it as a version-only bump if no API changes were made.💡 Suggested improvement
- `light-compressed-account` v0.10.1 - `compressed_mint` photon API support. (`#2198`) -- `light-token-client` v0.21.0 +- `light-token-client` v0.21.0 - Version bump (no API changes).🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@changelog.mdx` around lines 156 - 157, Update the changelog entry for "light-token-client v0.21.0" to include a short description or note; locate the entry `light-token-client v0.21.0` in changelog.mdx and either add a one-line summary of the change (e.g., bugfix, feature, API change) or explicitly mark it as a "version-only bump" if there were no API/behavior changes.
8-158: Consider adding GitHub release links for detailed changelogs.The PR objectives mention GitHub release links for each version, but they're not included in the changelog entries. Adding direct links would help users access the full release notes and associated commits.
For example, under each section header:
### light-registry v2.2.0 [Full release notes](https://github.com/Lightprotocol/light-protocol/releases/tag/light-registry-v2.2.0)This is optional if the changelog intentionally keeps a concise format.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@changelog.mdx` around lines 8 - 158, Add explicit GitHub release links under each package section header (e.g., "light-registry v2.2.0", "light-token v0.22.1", "photon-api v0.55.0", etc.) so users can jump to full release notes; for each header insert a single-line link like "Full release notes: https://github.com/Lightprotocol/light-protocol/releases/tag/{package-name}-{version}" replacing {package-name} and {version} with the crate name and version used in that header, and ensure the link text and URL are consistent across all Update sections in changelog.mdx.
38-40: Consider specifying which CHANGELOG to reference.The warning directs users to "the CHANGELOG" for migration steps, but doesn't specify which one. Consider linking directly to the relevant CHANGELOG file or release notes to help users find the migration instructions more easily.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@changelog.mdx` around lines 38 - 40, The warning text "Breaking changes in this release. See the CHANGELOG for migration steps." is ambiguous; update the Warning block to reference the exact changelog or release notes. Replace the generic "the CHANGELOG" inside the <Warning> block with a specific link or filename (for example the repository's CHANGELOG.md or the release notes URL) and/or add an inline anchor to the relevant migration section so readers land directly on the migration steps.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@changelog.mdx`:
- Around line 156-157: Update the changelog entry for "light-token-client
v0.21.0" to include a short description or note; locate the entry
`light-token-client v0.21.0` in changelog.mdx and either add a one-line summary
of the change (e.g., bugfix, feature, API change) or explicitly mark it as a
"version-only bump" if there were no API/behavior changes.
- Around line 8-158: Add explicit GitHub release links under each package
section header (e.g., "light-registry v2.2.0", "light-token v0.22.1",
"photon-api v0.55.0", etc.) so users can jump to full release notes; for each
header insert a single-line link like "Full release notes:
https://github.com/Lightprotocol/light-protocol/releases/tag/{package-name}-{version}"
replacing {package-name} and {version} with the crate name and version used in
that header, and ensure the link text and URL are consistent across all Update
sections in changelog.mdx.
- Around line 38-40: The warning text "Breaking changes in this release. See the
CHANGELOG for migration steps." is ambiguous; update the Warning block to
reference the exact changelog or release notes. Replace the generic "the
CHANGELOG" inside the <Warning> block with a specific link or filename (for
example the repository's CHANGELOG.md or the release notes URL) and/or add an
inline anchor to the relevant migration section so readers land directly on the
migration steps.
There was a problem hiding this comment.
🧹 Nitpick comments (2)
changelog.mdx (2)
204-211: Missing description and PR reference forlight-token-client.Line 209 lists
light-token-clientv0.21.0 without a description or PR reference, unlike the other entries in this section. Consider adding the relevant details for consistency.- `light-program-test` v0.21.0 - `compressed_mint` photon API support. (`#2198`) - `light-compressed-account` v0.10.1 - `compressed_mint` photon API support. (`#2198`) -- `light-token-client` v0.21.0 +- `light-token-client` v0.21.0 - dependency bumps. (`#XXXX`)🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@changelog.mdx` around lines 204 - 211, In the "### Other SDK updates" section update the `light-token-client` v0.21.0 entry to match the other items by adding a short description (e.g., what changed such as "compressed_mint photon API support" or the specific feature/fix) and append the PR reference in parentheses (e.g., (#####)) so the line reads consistently like the other SDK entries; edit the `light-token-client` v0.21.0 line to include the descriptive text and the PR number.
8-211: Consider adding links to GitHub releases.The PR description mentions that release notes include links to corresponding GitHub releases (e.g.,
light-registry-v2.2.0,light-token-v0.22.1, etc.), but these links don't appear in the changelog content. Adding direct links to the GitHub release pages would help users access detailed changelogs and migration guides.For example:
### light-registry v2.2.0 +[View release on GitHub](https://github.com/Lightprotocol/light-protocol/releases/tag/light-registry-v2.2.0) + `light-registry` v2.2.0 deployed to devnet...🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@changelog.mdx` around lines 8 - 211, Add GitHub release links for each release entry by turning the package/version mentions (e.g., "light-token v0.23.0", "light-sdk-macros v0.23.0", "light-registry v2.2.0", "light-token v0.22.1", etc.) into direct links to their GitHub release pages (e.g., https://github.com/<org>/<repo>/releases/tag/vX.Y.Z) or append a "(release)" link next to each Update label; update the sections that list crate updates and the inline toml dependency lines to include the appropriate GitHub release URLs so users can click through to the full release notes.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@changelog.mdx`:
- Around line 204-211: In the "### Other SDK updates" section update the
`light-token-client` v0.21.0 entry to match the other items by adding a short
description (e.g., what changed such as "compressed_mint photon API support" or
the specific feature/fix) and append the PR reference in parentheses (e.g.,
(#####)) so the line reads consistently like the other SDK entries; edit the
`light-token-client` v0.21.0 line to include the descriptive text and the PR
number.
- Around line 8-211: Add GitHub release links for each release entry by turning
the package/version mentions (e.g., "light-token v0.23.0", "light-sdk-macros
v0.23.0", "light-registry v2.2.0", "light-token v0.22.1", etc.) into direct
links to their GitHub release pages (e.g.,
https://github.com/<org>/<repo>/releases/tag/vX.Y.Z) or append a "(release)"
link next to each Update label; update the sections that list crate updates and
the inline toml dependency lines to include the appropriate GitHub release URLs
so users can click through to the full release notes.
1 participant
Release Notes - February 2026
Update blocks (6)
GitHub Releases
Generated by OpenClaw release-notes automation.
Summary by CodeRabbit