diff --git a/.changeset/homebridge-teslemetry-same-name-major-cut.md b/.changeset/homebridge-teslemetry-same-name-major-cut.md
deleted file mode 100644
index 80892a6..0000000
--- a/.changeset/homebridge-teslemetry-same-name-major-cut.md
+++ /dev/null
@@ -1,7 +0,0 @@
----
-"homebridge-teslemetry": major
----
-
-Publish the monorepo Homebridge plugin under the same npm name as the legacy `homebridge-teslemetry` package, superseding it with a major version (1.0.0 over legacy 0.4.x). This is a hard cut, not a parallel release - there is no dual-maintenance and no rename; going forward `homebridge-teslemetry` on npm is this package.
-
-**Breaking: the HomeKit service set has changed.** The legacy plugin registered 14 vehicle services and 7 energy services. This package registers 11 vehicle services and 6 energy services, and is subType-aware for services that previously collided under a shared HomeKit service type (e.g. `LockService`/`ChargePortService` both used `Service.LockMechanism`; several switches shared `Service.Switch`). Existing users upgrading from the legacy package should expect some HomeKit accessories/tiles to disappear, merge, or need re-pairing in the Home app after upgrade - this is expected, not a regression.
diff --git a/packages/homebridge-teslemetry/CHANGELOG.md b/packages/homebridge-teslemetry/CHANGELOG.md
index 9326dd4..2dedd6e 100644
--- a/packages/homebridge-teslemetry/CHANGELOG.md
+++ b/packages/homebridge-teslemetry/CHANGELOG.md
@@ -1,5 +1,13 @@
 # @teslemetry/homebridge-teslemetry
 
+## 2.0.0
+
+### Major Changes
+
+- 74e9990: Publish the monorepo Homebridge plugin under the same npm name as the legacy `homebridge-teslemetry` package, superseding it with a major version (1.0.0 over legacy 0.4.x). This is a hard cut, not a parallel release - there is no dual-maintenance and no rename; going forward `homebridge-teslemetry` on npm is this package.
+
+  **Breaking: the HomeKit service set has changed.** The legacy plugin registered 14 vehicle services and 7 energy services. This package registers 11 vehicle services and 6 energy services, and is subType-aware for services that previously collided under a shared HomeKit service type (e.g. `LockService`/`ChargePortService` both used `Service.LockMechanism`; several switches shared `Service.Switch`). Existing users upgrading from the legacy package should expect some HomeKit accessories/tiles to disappear, merge, or need re-pairing in the Home app after upgrade - this is expected, not a regression.
+
 ## 0.1.11
 
 ### Patch Changes
diff --git a/packages/homebridge-teslemetry/package.json b/packages/homebridge-teslemetry/package.json
index 1241ef7..f69dc24 100644
--- a/packages/homebridge-teslemetry/package.json
+++ b/packages/homebridge-teslemetry/package.json
@@ -1,7 +1,7 @@
 {
   "name": "homebridge-teslemetry",
   "displayName": "Homebridge Teslemetry",
-  "version": "1.0.0",
+  "version": "2.0.0",
   "description": "Teslemetry integration for Homebridge with real-time streaming support",
   "author": "Teslemetry",
   "license": "Apache-2.0",