docs: record P30's registry.json blind spot and the P31 CI archaeology - #29
Merged
Merged
Conversation
Answering "was P30 actually complete" surfaced one real gap not caught by P30's own verification (ng test/build, registry-sync, registry-parity all check packages/ui + registry source and file existence — none of them diff registry.json's peerDependencies against actual imports). Documented it as an addendum to P30, and gave the CI investigation from this PR (test-cli's missing sync-registry step, the picocolors CI-only ANSI pollution, and the manual-version-bump-vs-changesets-bot mixup) its own P31 section, so a future session doesn't have to re-derive any of this from scratch. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
PR #27 got merged (along with the bot's #28 version PR) before this last commit made it in, so it never landed on
main. This is just that one commit, rebased clean on currentmain.DEVLOG.mddocumenting that its own verification (ng test/build, registry-sync, registry-parity) never diffsregistry.json'speerDependenciesagainst actual source imports — which is exactly how thetransfer→@lucide/angulardrift (fixed in chore: version @sanring/cli 0.23.3 -> 0.24.0 #27) slipped through undetected.test-cli's missingsync-registrystep, thepicocolors-under-CI=trueANSI pollution that broke 4 tests only in CI, and the manual-version-bump-vs-changesets-bot mixup.Docs-only change, no code touched.
🤖 Generated with Claude Code