-
Notifications
You must be signed in to change notification settings - Fork 40
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
New release? #50
Comments
@aspett Hey 👋, thank you for using Sage. Indeed they should be fixed and I'll push a release shortly, there is nothing you need to do about that 👍 |
Sage 0.6 is out, please try it and tell if there is something wrong. Thank you again 🎊 |
Hey @AndrewDryga thank you so much for that! I've updated it in one codebase, and so far so good. I noticed the removal of the |
@aspett I see your use case. I think we should do something different to support it, mainly because if we pass other stage names to compensations we tell people that compensation can have complex logic when it's better to push for their pure design. Maybe we can add some API to the Sage itself to only accept |
Hiya @AndrewDryga - we're using Sage quite a lot and have recently upgraded to elixir 1.10. We've noticed a lot of warnings on
0.4.0
, and I'd forked with the intention of cleaning them up and pull requesting, but I see that they're all actually fixed on master. Keen to understand your appetite for a 0.5.0 or 1.0.0 release (appears there are some breaking API changes), and if there's anything I can do to help get there?The text was updated successfully, but these errors were encountered: