Thanks Simon,
My development team is currently investigating what it will take for us to
migrate away from using cordova-plugin-globalization, but it will take some
time to get it scheduled and completed. So it will happen -- that's the good
news. The bad news is that it keeps our customers
Since this is a security issue that has already been merged I feel like we
should include globalization in the next plugin release.
John, you really should start planning to migrate away from this plugin as
we can't guarantee it will be updated in the future. There is a blog post
detailing an
We will probably do a plugins release after Easter with all plugins updated
since the last release, so we can include this and some other deprecated
plugins that also got an update.
2018-03-27 15:24 GMT+02:00 johnkger...@gmail.com :
>
>
> On 2018/03/26 21:23:26, Steven
On 2018/03/26 21:23:26, Steven Gill wrote:
> cordova-plugin-globalization was deprecated November 2017. See
> https://github.com/apache/cordova-plugin-globalization#deprecation-notice
>
> We aren't planning on doing anymore releases as far as I'm aware. We
> recommend
cordova-plugin-globalization was deprecated November 2017. See
https://github.com/apache/cordova-plugin-globalization#deprecation-notice
We aren't planning on doing anymore releases as far as I'm aware. We
recommend pointing your package.json & config.xml to the github repo
instead if you want to
Hi Team,
Pull request #64
(https://github.com/apache/cordova-plugin-globalization/pull/64) was committed
on February 2 to address a ReDoS issue in moment.js, which is shipped in
cordova-plugin-globalization. As this is a security issue, may I ask what the
current plans are for releasing a