Skip to content

chore: release main - #1387

Open
openfeaturebot wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

chore: release main#1387
openfeaturebot wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@openfeaturebot

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop


This PR was generated with Release Please. See documentation.

@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch from d844ced to b9414d5 Compare April 21, 2026 22:36
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Note

Gemini is unable to generate a review for this pull request due to the file types involved not being currently supported.

@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch 2 times, most recently from faad70b to 23a0d37 Compare April 21, 2026 22:48
@toddbaert
toddbaert requested review from a team as code owners April 21, 2026 22:57
@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch 3 times, most recently from 899e31d to 7177b9a Compare April 21, 2026 23:01
@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch 10 times, most recently from 669de10 to 89e8e2c Compare April 28, 2026 20:28
@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch from 89e8e2c to e0a8df6 Compare May 19, 2026 16:59
@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch from e0a8df6 to 9a65082 Compare June 1, 2026 18:19
@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch 2 times, most recently from 2eb0dac to 8fcab25 Compare June 12, 2026 16:29
@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch 4 times, most recently from 47415a0 to a7b4441 Compare June 12, 2026 16:49
@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch 17 times, most recently from df5fbf1 to 34abb24 Compare June 19, 2026 15:13
@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch from 34abb24 to af672e1 Compare July 27, 2026 20:57
@coderabbitai

coderabbitai Bot commented Jul 27, 2026

Copy link
Copy Markdown

Review Change Stack

Warning

Review limit reached

@openfeaturebot, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 49 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6f3c0e20-07c0-4fc3-bf3e-8ea3077208ed

📥 Commits

Reviewing files that changed from the base of the PR and between af672e1 and 6348edd.

📒 Files selected for processing (3)
  • .release-please-manifest.json
  • packages/nest/CHANGELOG.md
  • packages/nest/package.json
📝 Walkthrough

Walkthrough

Package release metadata was updated for Angular, NestJS, and React. Patch versions were incremented, OpenFeature development dependencies were pinned to newer versions, changelogs were updated, and the release manifest was synchronized.

Changes

Package release updates

Layer / File(s) Summary
Release manifest version alignment
.release-please-manifest.json
The manifest increments the NestJS package to 0.2.8 and the Angular SDK package to 1.3.2.
Angular and React dependency release metadata
packages/angular/projects/angular-sdk/package.json, packages/angular/projects/angular-sdk/CHANGELOG.md, packages/react/package.json, packages/react/CHANGELOG.md
Angular and React patch versions are incremented, OpenFeature dependencies are pinned, and changelogs record the dependency updates.
NestJS dependency release metadata
packages/nest/package.json, packages/nest/CHANGELOG.md
The NestJS patch version is incremented, OpenFeature dependencies are updated, and the changelog records the dependency updates.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: aepfli

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title matches an automated release PR for the main branch and is related to the version and changelog updates.
Description check ✅ Passed The description is clearly about an automated Release Please release PR, which matches the package version and changelog updates.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

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

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/angular/projects/angular-sdk/CHANGELOG.md`:
- Line 3: Change the Dependencies heading from H3 to H2 in
packages/angular/projects/angular-sdk/CHANGELOG.md lines 3-3,
packages/react/CHANGELOG.md lines 3-3, and packages/nest/CHANGELOG.md lines 3-3,
keeping the heading text unchanged.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 26ff8800-a64d-4313-8d1c-048322e6bf6f

📥 Commits

Reviewing files that changed from the base of the PR and between a98f914 and af672e1.

📒 Files selected for processing (7)
  • .release-please-manifest.json
  • packages/angular/projects/angular-sdk/CHANGELOG.md
  • packages/angular/projects/angular-sdk/package.json
  • packages/nest/CHANGELOG.md
  • packages/nest/package.json
  • packages/react/CHANGELOG.md
  • packages/react/package.json

@@ -1,5 +1,12 @@
# Changelog

### Dependencies

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Correct the changelog heading level consistently.

The newly added Dependencies headings are H3 headings where markdownlint expects H2 headings.

  • packages/angular/projects/angular-sdk/CHANGELOG.md#L3-L3: change ### Dependencies to the expected H2 level.
  • packages/react/CHANGELOG.md#L3-L3: change ### Dependencies to the expected H2 level.
  • packages/nest/CHANGELOG.md#L3-L3: change ### Dependencies to the expected H2 level.
🧰 Tools
🪛 markdownlint-cli2 (0.23.0)

[warning] 3-3: Heading levels should only increment by one level at a time
Expected: h2; Actual: h3

(MD001, heading-increment)

📍 Affects 3 files
  • packages/angular/projects/angular-sdk/CHANGELOG.md#L3-L3 (this comment)
  • packages/react/CHANGELOG.md#L3-L3
  • packages/nest/CHANGELOG.md#L3-L3
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@packages/angular/projects/angular-sdk/CHANGELOG.md` at line 3, Change the
Dependencies heading from H3 to H2 in
packages/angular/projects/angular-sdk/CHANGELOG.md lines 3-3,
packages/react/CHANGELOG.md lines 3-3, and packages/nest/CHANGELOG.md lines 3-3,
keeping the heading text unchanged.

Source: Linters/SAST tools

Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
@openfeaturebot
openfeaturebot force-pushed the release-please--branches--main branch from 772eca4 to 6348edd Compare July 28, 2026 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant