TensorFlowLiteTaskText requires outdated GoogleToolboxForMac about tflite-support HOT 11 CLOSED

Sound reasonable to me.

Any thoughts @yyoon and @lu-wang-g ?

Thanks,
Tiezhen

from tflite-support.

Sounds good to me.

@lu-wang-g @xunkai55 Should we push a new version with this change?

from tflite-support.

A new version will be great! As we are soon releasing TFLite Support 2.5 on the Java side, so it will be great to push for a new Cocoapods version. @xunkai55 is the Cocoapods release under your plan?

Also, is it possible to pin to the major version as suggested?

from tflite-support.

A new version will be great! As we are soon releasing TFLite Support 2.5 on the Java side, so it will be great to push for a new Cocoapods version. @xunkai55 is the Cocoapods release under your plan?

I think we should rather publish 0.1.1 ASAP with only the dependency constraint change from 0.1.0. This should unblock any users having the same issues right now. I can proceed with that if you're okay with it.

Also, is it possible to pin to the major version as suggested?

Yes, that's well supported by CocoaPods, as suggested by @tinder-owenthomas. I'd prefer we specify ~> 2.2.1 as we haven't really tested it between [2.0.0, 2.2.1).

from tflite-support.

@yyoon sounds good! Actually, it's not TFLite Support 2.5; it's TFLite Support 0.2, which depends on TFLite 2.5. But anyway, 0.1.1 sounds good to me. Thanks a lot!

from tflite-support.

@tinder-owenthomas I've just published TensorFlowLiteTaskText pod version 0.1.1 with the modified dependency constraint.

I'm closing this for now, but please feel free to reopen if the issue hasn't been properly resolved.

from tflite-support.

Thanks for looking into this @yyoon!

It looks like right now it is pinned at ~> 2.2.1 which will allow for patch updates, but only as far as 2.2.2 (as that's the last 2.2 patch they issued). Any chance we can pin at ~> 2.2 without the patch specifier to allow any 2.x.x version? Google is up to 2.3.1 now which is what our other dependencies are looking for, and will presumably bump to 2.4.x in the near future - but assuming they are following proper semantic versioning there will not be breaking changes until they go to a new 3.x.x major version so any 2.x.x should be ok.

from tflite-support.

Oh, somehow I didn't realize CocoaPods would lock the minor version as well when specifying the patch.
Yeah, the intended behavior is the one you described with ~> 2.2. I'll try updating this again and let you know.

from tflite-support.

@tinder-owenthomas This should be fixed by now. Could you repo update and try again?

from tflite-support.

Seems to be working. Thank you!

from tflite-support.

Thanks for confirming!

from tflite-support.