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

update dependency to autoform 6.0.0 #9

Closed
abate opened this issue May 15, 2017 · 8 comments
Closed

update dependency to autoform 6.0.0 #9

abate opened this issue May 15, 2017 · 8 comments

Comments

@abate
Copy link

abate commented May 15, 2017

Thanks !

@raiyankamal
Copy link
Collaborator

Hi @abate, I'll be happy to accept some contribution on this issue. I'm currently unable to allocate time to work on this project. If you already have a solution, feel free to send me a pull request. Cheers.

@abate
Copy link
Author

abate commented May 16, 2017

I've tested this package with the new autoform locally. You just need to add aldeed:[email protected] as the package dependency and make a new release . that's all. I can prepare a PR, but I guess it will take less time to just do it yourself.

@jankapunkt
Copy link
Member

@abate and all who still are interested in this package - there will be an update within the upcoming week to the latest noUISlider version and AutoForm versions. Backwardcompatibility still needs to be tested.

@raiyankamal
Copy link
Collaborator

Happy new year to all!

@raiyankamal
Copy link
Collaborator

@jankapunkt let me know when you are ready for a release. Or if you have any roadblocks that I might be able to resolve. Thanks.

@jankapunkt
Copy link
Member

jankapunkt commented Jan 1, 2019

@raiyankamal I tested with my app the version bump and there were no problems. I would merge the 0.5 branch with master so you could publish the up-to-date version.

Edit: Happy new year 👍

@jankapunkt
Copy link
Member

Please see #12

@raiyankamal
Copy link
Collaborator

@jankapunkt your PR is merged. I made another branch 0.4.1 to update the docs a little bit and also for keeping a separate release branch for that version just in case. Have a look at the PR: #14
We can move ahead with the release once this one is merged.

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

No branches or pull requests

3 participants