-
-
Notifications
You must be signed in to change notification settings - Fork 3
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
semver dependency #91
Comments
Thanks, will fix tomorrow. |
seems it has been reverted |
looking into it now |
fixed in v3.15.0 - sorry again! - seems that I fixed it in boundation, but then the routine automated sweep was using an old version of boundation - I'll check in the future on automated sweeps that this doesn't happen again |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In 3.11.0, semver moved from dependencies to devDependencies so is failing to import when I use a module that depends on editions in a Docker image that only contains production dependencies.
The text was updated successfully, but these errors were encountered: