Chore: new ff release

[EnzalRad]

Summary by CodeRabbit

• New Features

  • Added infrastructure provider to runner context.

• Documentation

  • Updated changelog for version 0.4.0.

• Chores

  • Bumped package version to 0.4.0.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
react-ui	Ready	Preview	Comment	Dec 10, 2025 9:48am

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Walkthrough

This pull request bumps the version of the feature-flag package from 0.3.0 to 0.4.0 and updates the changelog with a new minor release section documenting the addition of an Infrastructure provider to the runner context.

Changes

Cohort / File(s)	Summary
Feature-flag package release libs/node/feature-flag/CHANGELOG.md, libs/node/feature-flag/package.json	Version bumped to 0.4.0 with changelog entry documenting the addition of Infrastructure provider to runner context

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

• Version bump is straightforward and confined to package metadata
• Changelog entry is a single line referencing a feature added elsewhere
• No logic, dependencies, or structural changes to review

Possibly related PRs

• New version release #138: Modifies the same feature-flag package with related runner-context changelog entries and version management

Suggested reviewers

• noe-charmet
• dvxam

Poem

🐰 A version hops up, from three to four,
Infrastructure in the runner's core,
With context fresh and providers new,
The feature-flag does what it's meant to do! 🚀

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)

Check name	Status	Explanation	Resolution
Title check	❓ Inconclusive	The title 'Chore: new ff release' is vague and does not clearly specify what changed. It uses generic phrasing ('new ff release') without indicating the specific component or version bump details.	Consider using a more descriptive title such as 'Chore: bump feature-flag package to 0.4.0' or 'Chore: release feature-flag v0.4.0 with infrastructure provider context' to clarify the specific changes.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

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

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 01ab726 and 64e7808.

📒 Files selected for processing (2)

• libs/node/feature-flag/CHANGELOG.md (1 hunks)
• libs/node/feature-flag/package.json (1 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

**/*

⚙️ CodeRabbit configuration file

We handle errors at the edge of our applications in most cases. Do not recommend to add error handling around every single function. We prefer them to bubble up and be handled at upper layers.

Files:

• libs/node/feature-flag/CHANGELOG.md
• libs/node/feature-flag/package.json

🔇 Additional comments (1)

libs/node/feature-flag/package.json (1)

5-5: Version bump is correct.

The version field is properly updated to 0.4.0, consistent with the minor feature addition documented in the changelog.

[coderabbitai]

⚠️ Potential issue | 🔴 Critical

Fix malformed version number in changelog.

The version header is written as "0..0" (double dot), which is invalid semantic versioning. It should match the version in package.json (0.4.0).

-## 0..0
+## 0.4.0

📝 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

	## 0..0
	### Minor Changes
	- a0bf18a: Add Infrastructure provider to runner context
	## 0.4.0
	### Minor Changes
	- a0bf18a: Add Infrastructure provider to runner context

🤖 Prompt for AI Agents

In libs/node/feature-flag/CHANGELOG.md around lines 3 to 7 the release header is
written as "## 0..0" which is malformed; update that header to the correct
semantic version "## 0.4.0" (matching package.json) and ensure any other
changelog references to the version are consistent with package.json.