From dd79cb606baaeb27b22d84f449b4023085d6c710 Mon Sep 17 00:00:00 2001 From: Rodrigo Date: Mon, 28 Mar 2022 17:16:54 -0500 Subject: [PATCH 1/2] Update README --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index a3bb0c2..3bf987d 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,6 @@

Welcome to onesignal-expo-plugin 👋

- Version + Version Documentation @@ -17,7 +17,6 @@ * 🏠 [Homepage](https://github.com/OneSignal/onesignal-expo-plugin#readme) * 🖤 [npm](https://www.npmjs.com/package/onesignal-expo-plugin) -## 🚧 In Beta 🚧 ## Overview This plugin is an [Expo Config Plugin](https://docs.expo.dev/guides/config-plugins/). It extends the Expo config to allow customizing the prebuild phase of managed workflow builds (no need to eject to a bare workflow). For the purposes of OneSignal integration, the plugin facilitates automatically generating/configuring the necessary native code files needed to get the [OneSignal React-Native SDK](https://github.com/OneSignal/react-native-onesignal) to work. You can think of adding a plugin as adding custom native code. From 0e5f43d02c0cd9533bbd7cadb4914a6efe8b6281 Mon Sep 17 00:00:00 2001 From: Rodrigo Date: Mon, 28 Mar 2022 17:17:05 -0500 Subject: [PATCH 2/2] 1.0.0 Release Commit --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 25f7dff..6d20779 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "onesignal-expo-plugin", - "version": "1.0.0-beta11", + "version": "1.0.0", "description": "The OneSignal Expo plugin allows you to use OneSignal without leaving the managed workflow. Developed in collaboration with SweetGreen.", "main": "./app.plugin.js", "scripts": {