Repository navigation
chore: release main - #2128
Merged
Merged
chore: release main#2128
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
October 28, 2026 14:03
ef180cb to
c4c4a28
Compare
joker23
approved these changes
Oct 28, 2026
Contributor
Author
|
🤖 Created releases: 🌻 |
joker23
added a commit
that referenced
this pull request
Oct 28, 2026
…2130) ## Summary Step 3 of the cleanup described in #2129. The `release-as: 1.1.0` pin for `@launchdarkly/openfeature-cloudflare-server` did its job: release PR #2128 published version 1.1.0. This change removes the pin so release-please computes future versions from conventional commits again. This was the only `release-as` property in the configuration. 🤖 Generated with [Claude Code](https://claude.com/claude-code) <!-- devin-review-badge-begin --> --- <a href="https://app.devin.ai/review/launchdarkly/js-core/pull/2130" target="_blank"><picture><source media="(prefers-color-scheme: dark)" srcset="https://static.devin.ai/assets/gh-devin-review-dark.svg?v=4"><img src="https://static.devin.ai/assets/gh-devin-review-light.svg?v=4" alt="Devin Review"></picture></a> <!-- devin-review-badge-end --> <!-- CURSOR_SUMMARY --> --- > [!NOTE] > **Overview** > Removes the **`release-as": "1.1.0"`** override from the **`packages/sdk/openfeature-cloudflare-server`** entry in **`release-please-config.json`**. > > Future releases for that package will follow release-please’s normal versioning (conventional commits / changelog) instead of being forced to **1.1.0**. No runtime or SDK code changes. > > <sup>Reviewed by [Cursor Bugbot](https://cursor.com/bugbot) for commit 428288e. Bugbot is set up for automated code reviews on this repo. Configure [here](https://www.cursor.com/dashboard/bugbot).</sup> <!-- /CURSOR_SUMMARY -->
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
openfeature-cloudflare-server: 1.1.0
1.1.0 (2026-10-28)
Bug Fixes
This PR was generated with Release Please. See documentation.
Note
Overview
Release Please bumps
@launchdarkly/openfeature-cloudflare-serverfrom 1.0.10 to 1.1.0 in the manifest, package metadata, getting-started example, and changelog.The 1.1.0 notes call out the shipped fix from #2115: TypeScript consumers using
node16/NodeNextmodule resolution should get correct typings (including separateimport/requiretypes via packageexports). This PR does not change runtime code—only release bookkeeping for that fix.Reviewed by Cursor Bugbot for commit c4c4a28. Bugbot is set up for automated code reviews on this repo. Configure here.