Async-firebase

Latest version: v3.9.0

Safety actively analyzes 682449 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 9

1.2.0

Not secure
* Added instrumentation to cleanup Firebase message before it can gets send. This is requirements that Firebase put on
us, otherwise it fails with 400 error code, which basically says that payload is not well formed.

1.1.0

Not secure
* Update 3rd-party dependencies:
- `google-auth = "~1.27.1"`
- `httpx = "<1.0.0"`

1.0.0

Not secure
* Remastering main client.
* method ``build_common_message`` completely dropped in favor of concept of message structures (module ``messages``).

* the signature of method ``push`` has changed. From now on, it expects to receive instances of ``messages.*`` for
Android config and APNS config rather than raw data, which then has to be dynamically analyzed and mapped to the
most appropriate message type.

* static methods ``build_android_message`` and ``build_apns_message`` renamed to ``build_android_config`` and
``build_apns_config``.

* static methods ``build_android_config`` and ``build_apns_config`` return ``messages.AndroidConfig`` and
``messages.APNSConfig`` respectively and aimed to simplify the process of creating configurations.

* Introduce module ``messages`` the main aim is to simplify the process of constructing Push notification messages.
The module houses the message structures that can be used to construct a push notification payload.

* Fix CD workflow. Make step ``release`` dependent on ``create-virtualenv``.

* Update ``README.md`` with more examples.

* Every request to Firebase tagged with ``X-Request-Id``

0.4.0

Not secure
* Method ``push()`` no longer has parameter ``alert_text``. The parameter ``notification_body`` should be used
instead.

0.3.0

Not secure
* Fix version

0.2.0

* Update README.md

Page 8 of 9

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.