3.12.0

What's Changed

• Test with Node.js 22.x by @nicknovitski in #78
• Type-checking improvements by @nicknovitski in #80
• Replace cache action usage with setup-node cache by @nicknovitski in #79
• Remove values mock from test by @nicknovitski in #82
• yarn v1.x -> v4.4.1 by @nicknovitski in #83
• Configure dependabot to update devDependencies by @nicknovitski in #84
• Bump ts-jest from 29.1.2 to 29.2.5 in the jest group by @dependabot in #86
• Bump micromatch from 4.0.5 to 4.0.8 by @dependabot in #77
• codecov-action v1 -> v4 by @nicknovitski in #88
• 100% test coverage by @nicknovitski in #89
• Bump typescript from 5.5.4 to 5.6.2 by @dependabot in #92
• chore: Don't try to update eslint by @nicknovitski in #93
• Bump the eslint-config-universe by @dependabot in #94
• Remove fetch-mock by @nicknovitski in #95
• Bump typescript from 5.6.2 to 5.6.3 by @dependabot in #99
• chore: allow triggering tests workflow manually by @vonovak in #101
• fix(types): move expoPushToken to ExpoPushErrorReceipt details by @saifhalila in #97
• fix: add missing request body type by @vonovak in #102
• 3.12.0 by @douglowder in #103

New Contributors

• @nicknovitski made their first contribution in #78
• @vonovak made their first contribution in #101
• @saifhalila made their first contribution in #97

Full Changelog: v3.11.0...v3.12.0

v3.11.0

What's Changed

• Update README.md by @nurbxfit in #69
• fix error when npm run watch by @katayama8000 in #70
• Add expoPushToken to ExpoPushErrorReceipt type by @kjkurtz in #74
• chore: Refactor constants by @douglowder in #75
• fix: useFcmV1 should default to true and be deprecated by @douglowder in #76
• Bump braces from 3.0.2 to 3.0.3 by @dependabot in #73
• 3.11.0 by @douglowder in #81

New Contributors

• @nurbxfit made their first contribution in #69
• @kjkurtz made their first contribution in #74
• @douglowder made their first contribution in #75

Full Changelog: v3.10.0...v3.11.0

v3.10.0

• Changes toThrowError to toThrow in the test suite. Does not affect usage of this library.

v3.9.0

New features

• Add DeveloperError, ProviderError, and ExpoError as possible error codes under the detail field of a push receipt. These codes are used when a more precise error code is not available. #55

v3.8.0

New features

• Added useFcmV1 option for explicitly opting in or out from using FCM v1, as opposed to FCM Legacy. Setting useFcmV1 to true will forcibly choose FCM v1 if an FCM v1 JSON credential has been uploaded, setting it to false will forcibly choose FCM Legacy if a legacy FCM token has been uploaded, and leaving it undefined will let the server choose. Read the guide, which explains what that means and goes into more detail about the migration. After the expected date Google will shut down FCM Legacy, June 20th, this option won't do anything since all push notifications will need to use FCM v1.

v3.7.0

Changes:

• #52

v3.6.0

New Features

• Support for the accessToken constructor option for projects that have opted in to requiring an access token to send push notifications: #39

v3.5.1

Bug Fixes

• isExpoPushToken now accepts an argument of any type. It also is statically typed to let TypeScript know the return value indicates whether the argument is a possible Expo push token. (#36)

v3.5.0

New Features

• Export TypeScript types for ExpoPushSuccessTicket, ExpoPushErrorTicket, ExpoPushSuccessReceipt, and ExpoPushErrorReceipt (#33)
• Make private methods actually private in TypeScript (b5dfdc8)

v3.4.0

New Features

• Adds convenience syntax for sending the same push notification message to multiple recipients (4658ede)