Merge pull request #2431 from segmentio/develop

Release 22.5.1

Author: stayseesong

src/connections/sources/catalog/libraries/mobile/react-native/index.md

@@ -4,8 +4,8 @@ strat: react-native
 repo: analytics-react-native
 ---
 
-> info "Analytics React Native 2.0 Pilot"
-> Analytics React Native 2.0 is available as a public pilot. Use of this pilot is governed by Segment's [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/){:target="_blank"}. For more information, see the [Analytics React Native 2.0 GitHub repository](https://github.com/segmentio/analytics-react-native){:target="_blank"}.
+> info "Analytics for React Native 2.0 in Public Beta"
+> Analytics for React Native 2.0 is available in public beta and is governed by Segment's [First-Access and Beta terms](https://segment.com/legal/first-access-beta-preview/){:target="_blank"}. For more information, see the [Analytics for React Native 2.0 GitHub repository](https://github.com/segmentio/analytics-react-native){:target="_blank"}.
 
 Analytics for React Native makes it easy to send your data to any analytics or marketing tool without having to learn, test or implement a new API every time.
 
@@ -18,7 +18,7 @@ In cloud-mode, Analytics-React-Native functions as a normal Segment library. In
 
 > warning ""
 > When you bundle a destination’s device-mode SDK, the React Native library serves as a wrapper for the iOS or Android source libraries. To access the underlying destination code, it is necessary to write bridging code between the React Native wrapper, and the destination’s SDK.
-> 
+>
 > For example, if to configure deep linking or retrieve the Appsflyer ID in Appsflyer, or configure in-app messages or push notifications in Braze, you must write code to specifically access these methods from the destination SDK.
 
 ### Analytics-React-Native and Unique Identifiers

src/connections/sources/catalog/libraries/website/javascript/ajs-classic.md

@@ -9,8 +9,9 @@ strat: ajs
 
 Analytics.js, Segment's Javascript source, makes it simple to send your data to any tool without having to learn, test or implement a new API every time.
 
-> info "Analytics.js 2.0"
-> A new version of Analytics.js is available. Click [here](/docs/connections/sources/catalog/libraries/website/javascript/) for more information. For information about upgrading to Analytics.js 2.0, see [Upgrade to Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2).
+> warning "Deprecation of Analytics.js Classic"
+> On August 31, 2022, Segment will end support and maintenance for Analytics.js Classic, and on February 28, 2023,  Segment will remove access to Analytics.js Classic.
+> <br><br>[Upgrade to Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2) before access ends for Analytics.js Classic. See the [Analytics.js 2.0 docs](/docs/connections/sources/catalog/libraries/website/javascript/) to learn more about the new source.
 
 ## Getting Started
 

src/connections/sources/catalog/libraries/website/javascript/upgrade-to-ajs2.md

@@ -5,6 +5,10 @@ strat: ajs
 
 Analytics.js 2.0 is fully backward compatible with Analytics.js Classic when you use the default Segment snippet in a standard implementation. To upgrade your sources, follow the manual upgrade steps below, or see the schedule for automatic migration. As with all upgrades, Segment recommends that you start development on a non-production source to test the upgrade process and outcome, prior to upgrading your production sources.
 
+> warning "Deprecation of Analytics.js Classic"
+> On August 31, 2022, Segment will end support and maintenance for Analytics.js Classic, and on February 28, 2023,  Segment will remove access to Analytics.js Classic.
+> <br><br>Upgrade to Analytics.js 2.0 before access ends for Analytics.js Classic. See the [Analytics.js 2.0 docs](/docs/connections/sources/catalog/libraries/website/javascript/) to learn more about the new source.
+
 ## Manual upgrade
 
 To upgrade a source to Analytics.js 2.0:

src/guides/regional-segment.md

@@ -10,7 +10,7 @@ As Schrems II restricts the transfer of personal data to any processors establis
 
 The default region for all users is in Oregon, United States. Workspaces can be configured to use the EU West Data Processing Region ingest (for supported sources), process, filter, deduplicate, and archive data through Segment-hosted archives hosted in S3 AWS Dublin, Ireland. The regional infrastructure has the same [rate limits and SLA](/docs/connections/rate-limits/) as the default region.
 
-## Existing Users
+## Existing Workspaces
 To ensure a smooth transition from a US-based Segment workspace to an EU workspace, Segment will provide additional support and tooling to help with the transition later this year. Use the form link below to provide more information about your current setup and goals for transitioning.
 
 {% include components/ajs-cookie.html %}
@@ -68,9 +68,11 @@ Regional Segment in the EU changes the way you [configure the Data Lakes AWS env
 ### Warehouse Public IP Range
 Use Segment's custom CIDR `3.251.148.96/29` while authorizing Segment to write in to your Redshift or Postgres port. [BigQuery](/docs/connections/storage/catalog/bigquery/#getting-started) doesn't require you to allow a custom IP address.
 
-## Regional endpoint availability
+## Destination support and Regional endpoint availability
 
 > info "Don't see a regional endpoint for a tool you're using?"
 > As more of the partner tools you use (Sources and Destinations) start to support a regional endpoint, Segment will update this list. Your contact for that tool should have a timeline for when they're hoping to support regional data ingestion. You can also visit Segment's [support page](https://segment.com/help/contact/) for any Segment-related questions.
 
+The following destinations are supported in your EU Segment workspace. The Destination tools that provide an EU Regional endpoint are marked for easy identification (see above.)
+
 {% include content/regional-integrations-table.md %}