-
-
Notifications
You must be signed in to change notification settings - Fork 174
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
Release strategy #716
Comments
That sounds like a reasonable approach. |
This is a crucial dependency of a project I am attempting to update to Ember 4.0. |
@andsmedeiros not yet. I'll think about it and update the issue. |
Sounds like a fine approach. A new release (even another beta) would be appreciated |
Bump to humbly request a |
@fsmanuel any progress on this? Can I assist in any way? |
Once again requesting a beta release 😅 Who has release creds? @offirgolan |
Hey @zeppelin long time no see! I'll have a look at your PRs and anlredy think it'll help a lot. |
@fsmanuel thank you for your work. I almost decided to move from ember-cp-validations into other library. You saved us lot of time! Looking forward for 4.0.0-beta.13, 4.x and 5.x versions. We need all of them! |
I had made up my mind to move away from ember-cp-validations too because it did not work with Ember 4. Looking forward to the 4.x and 5.x, thanks @fsmanuel ! |
beta.13 is released. We'll need to replace the deprecated ember-cli-release process, esp since it doesn't work with OTP and the changelog generation seems broken (or maybe the commits aren't properly formatted). Should follow the guidelines in the adopted org. |
@knownasilya Thanks a lot. To all: Would be great to get some help with the release and guidelines as I'm not familiar setting up all that tools. |
@gilest @andsmedeiros @enterpub @JenLyndle can you test the |
@fsmanuel I will be able to test next week. We have a huge app with all kinds of validation, so I'll test it heavily. Thank you so much! |
@fsmanuel sure will do! thanks! |
@fsmanuel thanks a lot! I'll test it against my application and let you know of what comes out of it. |
@knownasilya Seems like there are not bugs or problems with the |
@knownasilya do you want to do the |
@knownasilya If you give me npm access I can do the release. |
Released |
#717 is looking for reviewers. |
Now that #717 has been merged, are we please able to get a release? |
@kiwi-josh I'll do a release in the next days and let you know. |
@kiwi-josh released |
As I mentioned before we have huge app with lot of different validation rules, sometimes complex (by using |
@enterpub Thanks for the feedback! |
My motivation to help working on the addon is to get rid of the annoying deprecations pointed out in #715
In the update process:
I figured out that it's not that simple to get it to work with ember
>=4
because the addon and probably the dependencies use the old ember imports and private apis that don't work anymore in ember 4.That raises the question how we should release new versions to have a happy update path. The latest released version is
4.0.0-beta.12
which was released over a year ago. NPM Versions show that most downloads are for the beta releases.My suggestion would be to release a version
4.0
that supports ember<=3.28.x
and after that work on a new5.0
release for ember>=4
. That would allow us to drop support for ember<=3.28.x
in the5.x
branch and make things much easier.We need to highlight breaking changes from the
ember-validators
dependency.I'm happy for more input and opinions.
volatile
option becausecomputed().volatile()
is removed:4.0.0-beta.13
4.0
issues Ember 4.0 compatibility - drops support for Ember < 3.28 #7174.0
for ember<=3.28.x
5.0
for ember>=4
ember-font-awesome
Update ember-cli to v4.4 and drop support for node v12 #731ember-data
imports Embroider: Use of ember-data internals #740embroider-safe
andembroider-optimized
scenarios Embroider: Use of ember internals #739The text was updated successfully, but these errors were encountered: