You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pull #1503 dropped node 16 support by updating to bfj ^8.0.0. Would it be possible to lock that dependency off until the package officially drops node 16 support in a major update?
The text was updated successfully, but these errors were encountered:
Right, PR I tagged should have been released under a major release, not a patch. Since it was released in a patch it breaks everyone on the current semver that previously supported the older node versions. It doesn't leave a version that Node 16 consumers can stay on and upgrade to the next major version that supports node 18 when they're ready
Pull #1503 dropped node 16 support by updating to
bfj ^8.0.0
. Would it be possible to lock that dependency off until the package officially drops node 16 support in a major update?The text was updated successfully, but these errors were encountered: