feat: cross-reference missing prs and pivot hugeicons to single-file#22
Merged
Conversation
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.
Sweep across every PR
@ramonclaudiohas filed upstream and reconcile against the README. Found four gaps and one pending pivot.dist/types/core-free-icons.d.ts+/// <reference path>directive) to a single-file inlinedeclare moduleblock at the top ofdist/types/index.d.ts. Avoids trippingoven-sh/bun#13330when bun applies the patch.getPackageByNamein expo's tools so canary tarballs stop shippingpeerDependencies.expo: "workspace:*"literal for scoped packages with mismatched dirs (@expo/ui,@expo/app-integrity). Without this,bun add @expo/ui@canaryerrors withWorkspace dependency "expo" not found.0.11.4and document in Closed. Was dropped in7a95e06when better-auth/better-auth#9345 made the upstream fix obsolete the client-side workaround. README never got the Closed entry.0.12.0shipped via #323).After this, every upstream PR
@ramonclaudiohas authored maps to a row in Open / Released / Closed, every patch dir on disk maps to a row, and every Filed issue is in the right state.