Skip to content

Releases: laravel-notification-channels/fcm

2.1.2

24 Nov 21:46
c2f085d
Compare
Choose a tag to compare
Add failed notification event (#64)

Fix Spaite Enum Issues

10 Sep 01:44
34a7fd9
Compare
Choose a tag to compare
2.1.1

fix: spatie/enum v3 compatibility fixes (#56)

Laravel 8.x Support

09 Sep 00:00
e19d2c1
Compare
Choose a tag to compare
2.1.0

Added Laravel 8.x support (#55)

Support Guzzle 7

21 Jul 11:29
4dbe175
Compare
Choose a tag to compare
2.0.4

Allow guzzle 7 (#46)

2.0.3

09 Jul 03:33
0f7db36
Compare
Choose a tag to compare
Upgrade kreait/laravel-firebase composer constraint version. Fixes #3…

2.0.2

30 Mar 15:49
ec070d4
Compare
Choose a tag to compare

Do an early return on empty tokens instead of throwing an exception. Fixes #18

2.0.1

06 Mar 04:19
225f63b
Compare
Choose a tag to compare

Fix Laravel 7 support

2.0.0

04 Mar 09:30
fff3112
Compare
Choose a tag to compare

FCM API calls has been migrated from legacy HTTP to HTTP v1 (docs from Firebase
here). This is a breaking change so notifications using v1.x should not upgrade to v2.x of this package unless you plan on migrating your notification classes.

1.7.0

05 Mar 02:45
Compare
Choose a tag to compare
  • Add Laravel 7 support
  • Expose notification Guzzle response objects

Initial release in `laravel-notification-channels` namespace

25 Jan 00:30
e315d5f
Compare
Choose a tag to compare
  • Drop support for laravel < 5.5 (#5)
  • Fix zero index $tokens (#3)