Repository navigation
chore: move the five adopted apps to the commits their Kiro Crew pins name - #68
Conversation
… name Each repository now carries the fixes that landed in Kiro Crew's built-in copy after it was cut, at a patch release (personal-shopper 0.1.1, papyrus 0.2.1, file-explorer 1.0.1, design-critique 1.0.1, pptx-maker 0.3.1). Moving the refs is what offers an already-adopted install the update.
Opus 5 Review — ✅ no blocking findingsOpus 5 completed its review of This comment is updated in place on each push. |
GPT 5.6 Review — ✅ no blocking findingsGPT 5.6 completed its review of This comment is updated in place on each push. Review detailsNo findings. |
App Readiness Review — ✅ no blocking findingsEvery app repository this PR adds or re-pins passed the blocking readiness rules at Rules: Review detailsAll five manifests read, all manifest-referenced paths globbed and confirmed present, both No findings. design-critique @ 36188055057a19bbc32783b278b9cacb433000ebNo findings. file-explorer @ e68646984d6825eade82dfbf067879d8b55441abNo findings. papyrus @ 6ca7bc697f39b78a5a4dba7bdf8d3e5eaa11348fNo findings. personal-shopper @ e3d71dec00e904c742b9992dbe043b06084c7facNo findings. pptx-maker @ 1c47c5099df4302f74de828407f87f193edea758No findings. [APP-READINESS-REVIEWED] 8b3df09 |
What
Moves the
refof five rows incatalog/official-registry.jsonto the commits that Kiro Crew's adoption pins now name. No other field or row changes.5ee04d99e3d71dec00e904c742b9992dbe043b06084c7fac54b741666ca7bc697f39b78a5a4dba7bdf8d3e5eaa11348f222feef8e68646984d6825eade82dfbf067879d8b55441aba2de30a036188055057a19bbc32783b278b9cacb433000ebd9ee01341c47c5099df4302f74de828407f87f193edea758Each commit is the head of its repository's
main. It carries the fixes that landed in Kiro Crew's built-in copy after the repository was cut, and its CI was green on ubuntu, macOS and Windows. An already-adopted install is an ordinary registry app, so this row is how it reaches those fixes: its record version is below the new one, so the store offers the update.Merge condition: right after the Kiro Crew pin PR
The Kiro Crew PR is kirodotdev/KiroCrew#31343. It moves the pins and the wheel versions. Each row's
noteasks forrefto equal the pin.would_downgrade), so nothing moves backwards. The pair just disagrees until this one lands.personal-shopper is also pinned at
5ee04d99onrelease/0.12.0. A 0.12.0 host adopts there first and is then offered 0.1.1 from this row. 0.1.1 keepsminKiroCrewVersion0.12.0.Verification
tools/format.py --check: all 3 files normalized.tools/validate.py: OK. The 3 warnings were already there, on other apps.pytest tests/: 522 passed.scripts/adoption_pin.py verifyreports all fiveok: each commit's git tree and codeload archive match the pin'streeSha256andarchiveSha256.