chore(main): release flagd-ofrep-cf-worker 0.0.2

[openfeaturebot]

🤖 I have created a release beep boop

0.0.2 (2026-03-31)

✨ New Features

• add R2 flag source support with per-token config loading (#2) (92f9c2e)
• add Rust OFREP worker with WASM support (d3dec1c)
• initial JS OFREP worker implementation (be8010a)

🐛 Bug Fixes

• disable CORS by default in the published artifact (#12) (714d49f)
• normalize repository URLs in package.json (#20) (d8c6be5)
• use disableDynamicCodeGeneration option in FlagdCoreOptions (a6fdbaf)

🧹 Chore

• add Apache-2.0 LICENSE and include it in published package (#16) (7769fa4)
• add release-please and npm publish workflow with OIDC (#18) (d4e5e56)
• align dev tooling with js-sdk and js-sdk-contrib (2b2d316)
• deps: update dependency @openfeature/flagd-core to v2 (#13) (0c7d3ff)
• fix TypeScript warnings and use logger in Targeting class (b30ec6f)
• migrate to ESLint 10 with flat config (#22) (f2beccd)
• pin js-sdk-contrib PR branch and add local build/test resolution mappings (42540ae)
• replace the flagd-core submodule with the released 1.3.0 package (#6) (7199cd5)
• update all dependencies to latest versions (394dd4c)
• upgrade to Node 25 and latest Cloudflare packages (e40c3a9)

📚 Documentation

• clean up root and package readmes (#7) (3ee157a)

🔄 Refactoring

• switch from custom implementation to forked flagd-core (e198b86)

---

This PR was generated with Release Please. See documentation.

[openfeaturebot]

🤖 Created releases:

• flagd-ofrep-cf-worker-v0.0.2

🌻

[gemini-code-assist]

Code Review

This pull request updates the js-ofrep-worker package to version 0.0.2. This version bump includes new features such as R2 flag source support and a Rust OFREP worker, along with several bug fixes, chore updates, documentation improvements, and refactoring. A review comment highlights that the generated CHANGELOG.md incorrectly lists a future release date, suggesting a potential misconfiguration in the release-please environment.

[gemini-code-assist]

The release date is set to 2026-03-31, which is in the future. This is likely a typo and should be corrected to the actual release date. Since this was generated by release-please, the environment where it's running might have an incorrect date configuration.