diff --git a/.changeset/launchdarkly-experimentation-config.md b/.changeset/launchdarkly-experimentation-config.md
deleted file mode 100644
index b48f994b..00000000
--- a/.changeset/launchdarkly-experimentation-config.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-'@flags-sdk/launchdarkly': major
----
-
-Support the native LaunchDarkly Marketplace integration.
-
-**Breaking changes:**
-
-- The default adapter (`ldAdapter`) now reads the Edge Config connection string from the `EXPERIMENTATION_CONFIG` environment variable instead of `EDGE_CONFIG`. This aligns with the native LaunchDarkly Marketplace integration and matches the behavior of other adapters (e.g. Statsig). `EDGE_CONFIG` is no longer read by the default adapter. The error thrown when `EXPERIMENTATION_CONFIG` is not set changed to `LaunchDarkly Adapter: Missing EXPERIMENTATION_CONFIG environment variable`.
-
-  **If you use the legacy LaunchDarkly Vercel integration** (which provides the connection string as `EDGE_CONFIG`), pass the connection string explicitly with `createLaunchDarklyAdapter`:
-
-  ```ts
-  import { createLaunchDarklyAdapter } from '@flags-sdk/launchdarkly';
-
-  const ldAdapter = createLaunchDarklyAdapter({
-    projectSlug: process.env.LAUNCHDARKLY_PROJECT_SLUG,
-    clientSideId: process.env.LAUNCHDARKLY_CLIENT_SIDE_ID,
-    edgeConfigConnectionString: process.env.EDGE_CONFIG,
-  });
-  ```
diff --git a/packages/adapter-launchdarkly/CHANGELOG.md b/packages/adapter-launchdarkly/CHANGELOG.md
index 690e907e..f3c7dbe0 100644
--- a/packages/adapter-launchdarkly/CHANGELOG.md
+++ b/packages/adapter-launchdarkly/CHANGELOG.md
@@ -1,5 +1,27 @@
 # @flags-sdk/launchdarkly
 
+## 1.0.0
+
+### Major Changes
+
+- [#418](https://github.com/vercel/flags/pull/418) [`5488865`](https://github.com/vercel/flags/commit/54888657e895d2c5e32f96baf545b9f798045c2c) Thanks [@mbrakken](https://github.com/mbrakken)! - Support the native LaunchDarkly Marketplace integration.
+
+  **Breaking changes:**
+
+  - The default adapter (`ldAdapter`) now reads the Edge Config connection string from the `EXPERIMENTATION_CONFIG` environment variable instead of `EDGE_CONFIG`. This aligns with the native LaunchDarkly Marketplace integration and matches the behavior of other adapters (e.g. Statsig). `EDGE_CONFIG` is no longer read by the default adapter. The error thrown when `EXPERIMENTATION_CONFIG` is not set changed to `LaunchDarkly Adapter: Missing EXPERIMENTATION_CONFIG environment variable`.
+
+    **If you use the legacy LaunchDarkly Vercel integration** (which provides the connection string as `EDGE_CONFIG`), pass the connection string explicitly with `createLaunchDarklyAdapter`:
+
+    ```ts
+    import { createLaunchDarklyAdapter } from "@flags-sdk/launchdarkly";
+
+    const ldAdapter = createLaunchDarklyAdapter({
+      projectSlug: process.env.LAUNCHDARKLY_PROJECT_SLUG,
+      clientSideId: process.env.LAUNCHDARKLY_CLIENT_SIDE_ID,
+      edgeConfigConnectionString: process.env.EDGE_CONFIG,
+    });
+    ```
+
 ## 0.3.4
 
 ### Patch Changes
diff --git a/packages/adapter-launchdarkly/package.json b/packages/adapter-launchdarkly/package.json
index dfa58aad..2659d392 100644
--- a/packages/adapter-launchdarkly/package.json
+++ b/packages/adapter-launchdarkly/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@flags-sdk/launchdarkly",
-  "version": "0.3.4",
+  "version": "1.0.0",
   "description": "LaunchDarkly provider for the Flags SDK",
   "keywords": [
     "flags-sdk",