Skip to content
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

FYI: new horast will be released, your code will break unless action is taken #9

Open
mbdevpl opened this issue Aug 27, 2019 · 1 comment

Comments

@mbdevpl
Copy link

mbdevpl commented Aug 27, 2019

I will release new incompatible version of horast soon. I'm using semver but I noticed in your requirements you have plain horast written, so your code will break unless you restrict the required version to <0.4.0, or alternatively, also update transpyle. Current transpyle depends on <0.4.0 but unfortunately also will break because it also has plain horast written in reqs. Although I'm using semver in my projects pretty consistently, I haven't been very good at specifying requirements in them until now ;) I'll be fixing that, but past versions will suffer...

@EraYaN
Copy link
Member

EraYaN commented Aug 27, 2019

Aah thanks for the heads up!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants