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 1 commit into
base: main
Choose a base branch
from
Open

docs: release notes for March 2026 releases #2323

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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 +5 to +9
Copy link
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.