Skip to content

feat(homebridge-teslemetry): same-name major hard cut over legacy package - #63

Merged
Bre77 merged 1 commit into
mainfrom
fm/hb-samename-major-cut
Jul 22, 2026
Merged

feat(homebridge-teslemetry): same-name major hard cut over legacy package#63
Bre77 merged 1 commit into
mainfrom
fm/hb-samename-major-cut

Conversation

@Bre77

@Bre77 Bre77 commented Jul 22, 2026

Copy link
Copy Markdown
Member

Intent

  • Captain ruling (2026-07-22): the monorepo Homebridge package does a same-name MAJOR hard cut over the legacy npm package - no dual-maintain, no rename. It must publish as unscoped homebridge-teslemetry, the same name the legacy package (currently 0.4.6, published manually via that repo's publish.sh) already uses on npm.
    • Renamed packages/homebridge-teslemetry/package.json from @teslemetry/homebridge-teslemetry to unscoped homebridge-teslemetry, bumped to 1.0.0 (clean major over legacy 0.4.x), and dropped private: true.
    • Updated every internal reference to the old scoped name: src/settings.ts's PLUGIN_NAME constant, the package README (badges, install/build/link commands), and AGENTS.md's package status line. workspace:* pin on @teslemetry/api is unchanged.
    • Added a major changeset documenting this as a breaking hard cut: legacy registered 14 vehicle + 7 energy HomeKit services, this package registers 11 vehicle + 6 energy (post subType-collision-fix) - existing legacy users should expect accessories to merge/disappear/need re-pairing after upgrading.
  • Not publishing in this PR. Because legacy homebridge-teslemetry was published by hand, npm OIDC trusted publishing is almost certainly not configured for that package name - the first CI publish of 1.0.0 may 404 or fail OIDC. This likely needs either a trusted-publisher config added on npm for homebridge-teslemetry, or a one-time manual npm publish (as was done for the other packages' first publishes). Flagging so this gets handled deliberately rather than surprising CI.

Build (pnpm build), typecheck (pnpm -r --no-bail tsc + iobroker.teslemetry's check), lint, and the full test suite (pnpm -r --no-bail test, 90/90 passing in homebridge-teslemetry) all pass under the new package name.

…kage

Rename the monorepo Homebridge package from @teslemetry/homebridge-teslemetry
to the unscoped homebridge-teslemetry, matching the legacy npm package it
supersedes, and bump to 1.0.0 (major over legacy 0.4.x) per captain ruling:
same-name hard cut, no dual-maintain, no rename. Removes private: true so
the package can publish, and adds a changeset documenting the breaking
HomeKit service-set differences from the legacy plugin.
@Bre77
Bre77 merged commit 74e9990 into main Jul 22, 2026
1 check passed
Bre77 added a commit that referenced this pull request Jul 24, 2026
…rd-cut bump (#65)

package.json was hand-bumped to 1.0.0 in #63 while also carrying a "major"
changeset. Changesets' major bump increments from whatever is currently in
package.json, so merging the auto-generated Version Packages PR would have
shipped 2.0.0, not the intended 1.0.0 landing over legacy 0.4.6. Reverting
to the pre-cut 0.1.11 baseline lets the existing changeset resolve to 1.0.0
as originally intended.
Bre77 added a commit that referenced this pull request Jul 28, 2026
…-name major hard cut (#70)

- Add publishConfig (access/provenance) and a package-local LICENSE file,
  matching the other publishable packages - the legacy 0.4.x package ships
  a LICENSE and the monorepo package had none.
- Fix the README's license/contributing links, which pointed at a root
  LICENSE/CONTRIBUTING.md that doesn't exist anywhere in this repo.
- Remove the config.schema.json/settings.ts latitude/longitude "Homelink"
  fields - Homelink was dropped in the #63 hard cut but the dead config
  survived, so real users would see a config option with no effect.
- Rewrite the stale "Phase 1/Phase 2 coming soon" feature list to match
  what's actually implemented in src/vehicle-services and src/energy-services.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant