Skip to content
Sarj Repo Standards
core/migration/workspace-membership-lost

Keep moved packages in their workspace

A relocated package remains selected by every same-ecosystem workspace that selected its old path.

warning beta

Examples

FlaggedFails
{"private":true,"workspaces":["apps/*"]}
PassesClean
{"private":true,"workspaces":["applications/*/*"]}

Why it matters

Package installs, builds, tests, and CI can silently omit the moved package.

How detection works

For a package beneath a migration target, reports when a same-ecosystem workspace included its reconstructed old path but does not include its new path.

What is inspected

  • Parser-backed package and workspace metadata from the exact selected Git tree.

Limits

  • Requiring every discovered package to belong to a workspace.
  • The rule reports only a workspace that selected the reconstructed old package path.

How to fix it

Update the native workspace declaration for the relocated package.

  1. Add a member pattern covering the package's new directory.
  2. Keep exclusions at least as narrow as they were before the relocation.

Verify

  • Run the package manager's immutable workspace install and repo-lint check.