Repository navigation
chore(packs): mark date-fns 3 to 4 as blocked in the queue - #73
Merged
Merged
Conversation
The v4.0.0 changelog lists only type-level breaking changes. No public repository with a compiler-visible v3 to v4 migration was found. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01TwUwACs2fD78dispBc1GkA Signed-off-by: Claude <noreply@anthropic.com>
lucasbraum
marked this pull request as ready for review
October 11, 2026 17:38
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
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.
Pack
date-fns
>=3 <4to>=4 <5(firsttodoentry inpacks/queue.json). No pack written: the entry is markedblocked, as the task's stop rule says when two public repositories with a real migration cannot be found.Sources
Ground-truth repositories (none usable)
Fewer than two repositories with a compiler-visible v3 to v4 migration, so the gate (verified needs >= 2) cannot be met and a candidate pack would have no ground truth.
uptide pack testoutputExisting packs, run on main before my change (queue.json is the only file touched):
verification.json does not match this run: uptide pack test react --write records it. Pre-existing on main, not caused by this PR; needs a maintainer to look at whether to re-record it.pnpm lint,pnpm typecheckandpnpm testpass.What isn't covered
Everything: no date-fns pack exists. The queue note also says the type diff does not match v4 subpath modules (
date-fns/add) yet, an engine limitation that would further understate findings.Tooling friction
scripts/packs-queue.tstypes status astodo | in-progress | candidate | verifiedand recomputes it on regeneration, soblockedandblockedReasonwill be dropped the next timepnpm packs:queueruns. I did not touch the script; a maintainer may want to preserveblocked.🤖 Generated with Claude Code
https://claude.ai/code/session_01TwUwACs2fD78dispBc1GkA
Generated by Claude Code