Goal
Eventually migrate the TypeScript client and native npm packages from the historical @kitlangton scope to the organization-owned @anomalyco scope, without breaking existing users.
Current State
- GitHub source repository has moved to
anomalyco/terminal-control.
- Existing npm packages remain under
@kitlangton for install continuity:
@kitlangton/terminal-control@kitlangton/terminal-control-darwin-arm64@kitlangton/terminal-control-darwin-x64@kitlangton/terminal-control-linux-arm64-gnu@kitlangton/terminal-control-linux-x64-gnu
- README and package metadata should point repository links at
anomalyco/terminal-control.
- npm trusted publishing for the existing
@kitlangton packages must use anomalyco/terminal-control + npm-release.yml.
Proposed Migration
- Keep publishing the existing
@kitlangton/... packages for now.
- Add parallel package definitions for the new
@anomalyco/... packages:
@anomalyco/terminal-control@anomalyco/terminal-control-darwin-arm64@anomalyco/terminal-control-darwin-x64@anomalyco/terminal-control-linux-arm64-gnu@anomalyco/terminal-control-linux-x64-gnu
- Update the client package native-binary resolution for the new scope so
@anomalyco/terminal-control depends on @anomalyco/terminal-control-*.
- Publish an initial
@anomalyco release at the same version as the current package line, or at the next coordinated version.
- Update docs to recommend
@anomalyco/terminal-control while documenting @kitlangton/terminal-control as the legacy package.
- After a transition period, deprecate the
@kitlangton/... npm packages with a message pointing users to @anomalyco/terminal-control.
- Continue avoiding npm unpublish so existing lockfiles and historical installs remain valid.
Acceptance Criteria
- Existing
@kitlangton/... packages remain installable.
- New
@anomalyco/... packages install and resolve the correct native binary on supported platforms.
- Release workflow can validate and publish both scopes, or has a clear switch-over workflow.
- README clearly explains the preferred package and legacy package status.
- npm trusted publishing is configured for all packages that GitHub Actions publishes.
Notes
Do this as a separate release task from the GitHub repository transfer. The package scope migration touches package names, optional dependencies, native package generation, validation fixtures, Changesets config, lockfile metadata, and npm trusted publisher settings.
Goal
Eventually migrate the TypeScript client and native npm packages from the historical
@kitlangtonscope to the organization-owned@anomalycoscope, without breaking existing users.Current State
anomalyco/terminal-control.@kitlangtonfor install continuity:@kitlangton/terminal-control@kitlangton/terminal-control-darwin-arm64@kitlangton/terminal-control-darwin-x64@kitlangton/terminal-control-linux-arm64-gnu@kitlangton/terminal-control-linux-x64-gnuanomalyco/terminal-control.@kitlangtonpackages must useanomalyco/terminal-control+npm-release.yml.Proposed Migration
@kitlangton/...packages for now.@anomalyco/...packages:@anomalyco/terminal-control@anomalyco/terminal-control-darwin-arm64@anomalyco/terminal-control-darwin-x64@anomalyco/terminal-control-linux-arm64-gnu@anomalyco/terminal-control-linux-x64-gnu@anomalyco/terminal-controldepends on@anomalyco/terminal-control-*.@anomalycorelease at the same version as the current package line, or at the next coordinated version.@anomalyco/terminal-controlwhile documenting@kitlangton/terminal-controlas the legacy package.@kitlangton/...npm packages with a message pointing users to@anomalyco/terminal-control.Acceptance Criteria
@kitlangton/...packages remain installable.@anomalyco/...packages install and resolve the correct native binary on supported platforms.Notes
Do this as a separate release task from the GitHub repository transfer. The package scope migration touches package names, optional dependencies, native package generation, validation fixtures, Changesets config, lockfile metadata, and npm trusted publisher settings.