docs: release notes for March 2026 releases

[klausundklaus]

Release Notes - 2026-03-02

Packages covered

• light-registry@2.2.1

GitHub Releases

• https://github.com/Lightprotocol/light-protocol/releases/tag/light-registry-v2.2.1

---

Generated by OpenClaw release-notes automation.

Summary by CodeRabbit

• New Features
  • Foresters can now register for an epoch at any time within the activation window, rather than being restricted to a designated registration phase.

[coderabbitai]

📝 Walkthrough

Walkthrough

A CHANGELOG.md entry is added documenting a behavioral change where is_registration_phase() no longer enforces registration time window restrictions. Foresters can now register for epochs anytime within the activation window rather than only during designated registration phases, addressing issue #2321.

Changes

Cohort / File(s)	Summary
Documentation programs/registry/CHANGELOG.md	Added entry documenting removal of registration time window enforcement in is_registration_phase(), allowing flexible epoch registration within activation windows.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🌲 The foresters rejoice, no timeline's cage,
Registration windows, now just a stage,
Any moment within the window's glow,
Their epochs beckon—let their seasons flow!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately reflects the changeset, which adds CHANGELOG.md documentation for the March 2026 release notes covering the light-registry package.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

Tip

Try Coding Plans. Let us write the prompt for your AI agent so you can ship faster (with fewer bugs).
Share your feedback on Discord.

---

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@programs/registry/CHANGELOG.md`:
- Around line 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.

---

ℹ️ Review info

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 14adf27 and 491d138.

📒 Files selected for processing (1)

• programs/registry/CHANGELOG.md

[coderabbitai]

🧹 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.