can we publish a release

[Techn1x]

I hate to be that guy but any chance we could get a patch release published? (please 😄 )

Hoping to consume the object assign deprecation fix #481

Otherwise it's a bit hard to see the forest from the trees in the dev console when booting up with a lot of models :)

[Techn1x]

(I know I can filter the console, I just want my output clean ✨ )

[RosarioAleCali]

I agree with @Techn1x... it would be much appreciated!

[Techn1x]

@patocallaghan friendly ping

[patocallaghan]

@Techn1x sorry for the delay. After looking into it. Fixing this deprecation is actually a major breaking change (drops IE11 support) so will have to do an alpha release and there are other breaking changes we’d like to get in. The alternative for you is to use something like patch-package and cherry pick the fix

[patocallaghan]

I’ll cut an alpha later but it won’t be the full major release version

[patocallaghan]

@Techn1x @RosarioAleCali I've released the change in v4.0.0-alpha.1. I've to update the release notes but FYI there are three breaking changes

• [BREAKING] Replace polyfill assign with Object.assign #481
• [BREAKING] Remove deprecated helpers #463
• [BREAKING] Fixes incompatibility with Ember Data Model Fragments 5.0.0-beta+ and Ember Data 3.13+ #449

[Techn1x]

Thanks Pat, that's a fair point and I think the alpha release is a good way to tackle it.

Given that this tool is for dev / testing, I do wonder if we need to care that much about dropping IE - but I understand the importance of semver :)

[patocallaghan]

@Techn1x Yeah you just don't know how folks are using this tool but at least following proper semver makes that versioning decision for us 👍