Skip to content
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

Support FCM HTTP v1 (async only) #4

Merged
merged 1 commit into from
Aug 29, 2024
Merged

Support FCM HTTP v1 (async only) #4

merged 1 commit into from
Aug 29, 2024

Conversation

sdb9696
Copy link
Owner

@sdb9696 sdb9696 commented Aug 29, 2024

Due to the deprecation of legacy FCM APIs provides support for the new FCM HTTP v1 apis.

@sdb9696 sdb9696 merged commit d78eef6 into main Aug 29, 2024
7 checks passed
@sdb9696 sdb9696 deleted the feat/fcm_http_v1 branch August 29, 2024 10:42
@sdb9696 sdb9696 added the enhancement New feature or request label Aug 29, 2024
@sdb9696 sdb9696 mentioned this pull request Aug 29, 2024
sdb9696 added a commit that referenced this pull request Aug 29, 2024
## [0.4.0](https://github.com/sdb9696/firebase-messaging/tree/0.4.0) (2024-08-29)

[Full Changelog](0.3.0...0.4.0)

**Release highlights:**

- Support for new FCM HTTP v1 API
- Previous versions of this library will no longer work due firebase [deprecating the legacy APIs](https://firebase.google.com/docs/cloud-messaging/migrate-v1)
- Dropping official python 3.8 support
- **Breaking** - this version of the library only supports being run in an asyncio event loop
- **Breaking** - The api has changed, see the readme for updated details

**Breaking change pull requests:**

- Drop python 3.8 support and update CI [\#5](#5) (@sdb9696)

**Implemented enhancements:**

- Support FCM HTTP v1 \(async only\) [\#4](#4) (@sdb9696)

**Project maintenance:**

- Update releasing instructions and add changelog [\#6](#6) (@sdb9696)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant