[Epic]: Self-updating and self-migrating PLATE in adopter repositories (v1.0.0)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 3
Description
Stub for additional must-have to enable the v1.0.0 vision.
Adopter repos can have PLATE itself evolve autonomously or semi-autonomously:
- Detect upstream changes in plate-core, template payload, AGENTS.md, workflows, skills
- Propose safe migration PRs (or apply at low risk tolerance)
- Verify post-migration health, update .plate, run bootstrap checks
- Preserve project-specific customizations
Critical for long-term "<30m onboarding" promise remaining true.
Parent: #627
Related: #633, #615, bootstrap, migration tooling, template sync scripts.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading parent issue #627 and related issues #633 and #615, then inspect the bootstrap, migration tooling, and template sync scripts mentioned here. Define the boundaries for detecting upstream changes, preserving customizations, proposing or applying migrations, and verifying post-migration health before implementation. Done means the v1.0.0 self-update and self-migration workflow is specified and validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devtools, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100