Skip to content

docs: release notes for March 2026 releases #2323

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
klausundklaus wants to merge 4 commits into
base: main
Choose a base branch
from
Open

docs: release notes for March 2026 releases #2323

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
491d138
docs: add release notes for 2026-03-02 releases
klausundklaus Mar 3, 2026
36abe61
docs: add release notes for 2026-03-10 releases
klausundklaus Mar 11, 2026
04919f3
docs: add release notes for light-registry v2.3.1 (2026-03-18)
klausundklaus Mar 18, 2026
8716cd8
docs: add release notes for JS SDKs v0.23.0 (2026-03-24)
klausundklaus Mar 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions programs/registry/CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
# Changelog

All notable changes to this package will be documented in this file.

## 2026-03-02

### Features

- `is_registration_phase()` no longer enforces the registration time window check. Foresters can now register for an epoch at any time within the activation window, not only during the designated registration phase. (#2321)
Comment on lines +38 to +42
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Mar 3, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Add explicit package/version + release link in this entry for traceability.

This entry explains the change well, but it currently omits the release artifact metadata. Adding light-registry@2.2.1 and the release URL on Line 5–Line 9 would make the note self-contained for audits and downstream consumers.

Suggested doc update 
 ## 2026-03-02

 ### Features

 - `is_registration_phase()` no longer enforces the registration time window check. Foresters can now register for an epoch at any time within the activation window, not only during the designated registration phase. (`#2321`)
+- Package: `light-registry@2.2.1`
+- Release: https://github.com/Lightprotocol/light-protocol/releases/tag/light-registry-v2.2.1
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
## 2026-03-02
### Features
- `is_registration_phase()` no longer enforces the registration time window check. Foresters can now register for an epoch at any time within the activation window, not only during the designated registration phase. (#2321)
## 2026-03-02
### Features
- `is_registration_phase()` no longer enforces the registration time window check. Foresters can now register for an epoch at any time within the activation window, not only during the designated registration phase. (`#2321`)
- Package: `light-registry@2.2.1`
- Release: https://github.com/Lightprotocol/light-protocol/releases/tag/light-registry-v2.2.1
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@programs/registry/CHANGELOG.md` around lines 5 - 9, Update the CHANGELOG
entry for 2026-03-02 to include the package name and version and a release link
for traceability: append "light-registry@2.2.1" and the canonical release URL
(e.g. GitHub/GitLab release page) to the Features bullet that mentions
is_registration_phase(), so the entry reads as a self-contained note containing
the affected symbol (is_registration_phase()), the package
(light-registry@2.2.1) and the release artifact URL.

Comment on lines +5 to +42
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Reconcile PR description with actual changelog content.

The PR description states it "Adds release notes for 2026-03-02. Packages covered: light-registry@2.2.1", but the file contains three distinct release entries (2026-03-18, 2026-03-10, and 2026-03-02). Additionally, the commit message references "light-registry v2.3.1 (2026-03-18)", not v2.2.1. This discrepancy makes it unclear which versions correspond to which dates and hampers release traceability.

Update the PR description to accurately reflect all three dates and their associated versions, or clarify whether this PR is meant to add only one entry.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@programs/registry/CHANGELOG.md` around lines 5 - 42, The PR description and
commit metadata disagree with the CHANGELOG.md entries: the changelog contains
three release entries (2026-03-18, 2026-03-10, 2026-03-02) and the commit
mentions "light-registry v2.3.1 (2026-03-18)" while the PR description claims
"light-registry@2.2.1"; update the PR description to precisely list each release
date and its corresponding package version (or state that this PR only adds the
2026-03-02 entry and move the other dates to separate PRs), and make the commit
message / tag match the version you choose; if the intention is a single-entry
change, remove the unintended entries from CHANGELOG.md or split them into
separate commits/PRs so the PR description, commit message, and CHANGELOG.md are
consistent (references: the literal changelog entries "2026-03-18",
"2026-03-10", "2026-03-02" and the version strings "light-registry@2.2.1" /
"light-registry v2.3.1").