Repository navigation
chore: Restore the openfeature-cloudflare-server version after an incorrect version tag - #2129
Merged
Merged
Conversation
…orrect version tag
Contributor
|
@launchdarkly/js-client-sdk size report |
Contributor
|
@launchdarkly/js-sdk-common size report |
Contributor
|
@launchdarkly/js-client-sdk-common size report |
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
tanderson-ld
approved these changes
Oct 28, 2026
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
![https://static.devin.ai/assets/gh-devin-review-dark.svg?v=4"><img](https://static.devin.ai/assets/gh-devin-review-dark.svg?v=4"><img){kind=link}
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.
This PR will release Openfeature Cloudflare SDK in the proper version. After this PR merges we will:
release-asconfig.The problem was that we did a minor version update while the release-please configuration for
@launchdarkly/openfeature-cloudflare-serverstill pinned the version to1.0.0... this seems to be fine for patch releases, but minor/major releases do not like this.We will delete the changelog entries and "rebase" the release to
1.0.10so that the next release-please run will accumulate the commits starting from that version tag.Note
Overview
Reverts
@launchdarkly/openfeature-cloudflare-serverfrom an erroneous 1.0.0 back to 1.0.10 in the package manifest,.release-please-manifest.json, and the getting-started example dependency.Removes duplicate 1.0.0 changelog sections that were introduced by the bad release, so history again starts at 1.0.10.
Updates
release-please-config.jsonso the next automated release is pinned withrelease-as:1.1.0(was1.0.0) as part of the follow-up release workflow described in the PR.Reviewed by Cursor Bugbot for commit f3da33e. Bugbot is set up for automated code reviews on this repo. Configure here.