feat(homebridge-teslemetry): same-name major hard cut over legacy package#63
Merged
Conversation
…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.
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
1 participant
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.
Intent
homebridge-teslemetry, the same name the legacy package (currently 0.4.6, published manually via that repo'spublish.sh) already uses on npm.packages/homebridge-teslemetry/package.jsonfrom@teslemetry/homebridge-teslemetryto unscopedhomebridge-teslemetry, bumped to1.0.0(clean major over legacy 0.4.x), and droppedprivate: true.src/settings.ts'sPLUGIN_NAMEconstant, the package README (badges, install/build/link commands), andAGENTS.md's package status line.workspace:*pin on@teslemetry/apiis unchanged.homebridge-teslemetrywas published by hand, npm OIDC trusted publishing is almost certainly not configured for that package name - the first CI publish of1.0.0may 404 or fail OIDC. This likely needs either a trusted-publisher config added on npm forhomebridge-teslemetry, or a one-time manualnpm 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'scheck), lint, and the full test suite (pnpm -r --no-bail test, 90/90 passing inhomebridge-teslemetry) all pass under the new package name.