Chore/new ff version

[EnzalRad]

Summary by CodeRabbit

• Patch

  • Version 0.4.1 released with maintenance updates.

• Tests

  • Corrected test description text for improved clarity.

• Refactor

  • Optimized code structure for better readability.

_{✏️ 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 10:45am

[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

The PR updates the feature-flag package to version 0.4.1, adds release notes for patch changes, corrects a test description string, and refactors the mapContext function to use a single-line object literal instead of multi-line structure.

Changes

Cohort / File(s)	Summary
Release metadata libs/node/feature-flag/CHANGELOG.md, libs/node/feature-flag/package.json	Version bumped to 0.4.1; new patch release entry added to changelog with "Force release trigger" note
Source code libs/node/feature-flag/src/index.ts, libs/node/feature-flag/src/index.test.ts	mapContext refactored to return single-line object literal; test description corrected (removed extra space)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

• Verify mapContext refactoring maintains equivalent functionality across all Context variants (especially the 'blank' case)
• Confirm version bump aligns with semantic versioning

Possibly related PRs

• Chore: new ff release #212: Previous release that bumped to 0.4.0 and introduced the "Add Infrastructure provider to runner context" feature; this PR follows as a patch release.

Suggested reviewers

• noe-charmet
• kylengn
• dvxam

Poem

🐰 Hopping through the code so neat,
Version bumped, the patch complete!
Objects formatted, single-line and clean,
Prettiest refactor ever seen! ✨
From 0.4.0 to 0.4.1 we hop,
A little force release that won't stop!

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Title check	❓ Inconclusive	The title 'Chore/new ff version' is vague and uses non-descriptive language that doesn't clearly convey what was changed.	Use a more descriptive title that specifies the actual changes, such as 'Release feature-flag v0.4.1 with bug fixes and formatting updates'.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

---

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

[kylengn]

Please resolve conflicts

The merge-base changed after approval.

Changes done