migrate(dev-tree): replace dev-lead symlink with !external resolver block (PR-D) #6
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "migrate/dev-lead-symlink-to-external"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Final phase of internal#77 (task #235). Completes the cross-repo composition migration:
dev-leadsymlink + sibling-clone deploy contract.!externalresolver + tests.org.yamlto!external. Composition is now platform-side at import time — no operator-side filesystem prep required.Changes
dev-leadsymlink deleted..gitignoreadds.external-cache/(platform-mutated cache; we don't track it).Deployment impact
Operators running molecule-core PR #105 or later can import this template without operator-side
molecule-dev-departmentclone — task #230 becomes obsolete. Operators running an older platform binary will see import fail withunknown !external tag— visible error, not silent breakage.Production stability path: tag
molecule-ai/molecule-dev-department v1.0.0and pinref: v1.0.0here.Verified locally (2026-05-08)
Clean room test: cloned this branch into a temp dir, ran
resolveYAMLIncludesagainstorg.yaml. Resolver fetchesmolecule-ai/molecule-dev-department@mainfrom Gitea into the cache, grafts the dev tree, applies path rewrite. Final tree: 5 PM-tree + 6 Marketing-tree + 28 dev-tree = 39 workspaces — same shape as before, now via!externalinstead of symlink.Versioning / backwards compat
No DB schema change. No public API change. Pure org-template composition shape change.
Existing imports of older snapshots of this template still work —
!include+ symlink were never the only composition mechanism, and operators who have the symlink can re-add it locally if they need to roll back. The platform's!includeresolver still supports symlinks (per molecule-core#102 contract test), this PR just stops the parent template from using one.Follow-up tasks (filed separately, not in this PR)
molecule-ai/molecule-dev-department/.molecule-ci/scripts/local-e2e-setup.shto drop the symlink check (now that parent template doesn't ship one).TestLocalE2E_DevDepartmentExtraction+TestLocalE2E_FilesDirConsumption— they tested the symlink-based composition. Now skip gracefully (no template uses that shape). Keep as opt-in regression coverage.molecule-ai/molecule-dev-department v1.0.0and pinrefhere for production stability.Refs
!externalresolver!externalintegration + e2e tests