-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pin [email protected] #7763
Pin [email protected] #7763
Conversation
Also bump msgpackr@^1.5.4 to avoid the duplicate dependency
|
Benchmark ResultsKitchen Sink 🚨
Timings
Cold BundlesNo bundles found, this is probably a failed build... Cached BundlesNo bundles found, this is probably a failed build... React HackerNews ✅
Timings
Cold BundlesNo bundle changes detected. Cached Bundles
AtlasKit Editor ✅
Timings
Cold Bundles
Cached BundlesNo bundle changes detected. Three.js ✅
Timings
Cold BundlesNo bundle changes detected. Cached Bundles
|
* upstream/v2: (26 commits) Replace typeof before DCE (#7788) Bump lmdb (#7797) Upgrade flow to 0.173.0 (#7809) Prevent `term-size` from being bundled (#7750) Pin [email protected] (#7763) Fix Windows CI (#7774) Upgrade Flow to 0.171.0 (#7667) Move tests to GitHub actions (#7678) v2.3.2 Fix autoinstalling node builtins (#7735) Fix lint Use pinned versions Don't build native packages again during publish step Fix build Fix autoinstall v2.3.1 Add diagnostic for failed autoinstall of node polyfill (#7682) v2.3.0 Changelog for 2.3.0 Support React 18 prereleases and experimental versions with automatic JSX runtime (#7642) ...
Also bump msgpackr@^1.5.4 to avoid the duplicate dependency.
Short synopsis (See this comment for a more authoritative story):
This PR pins the version of lmdb to avoid the possibility of installing a version that might trigger the race.
We will be trading the ability for lmdb to ship fixes for Parcel users without a new Parcel release, but many projects will have a lockfile that effectively prevents upgrading lmdb without a bump from Parcel, anyway.
Related: