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

Update rnm-getting-started.md to recommend using 0.75 #969

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

gabrieldonadel
Copy link

@gabrieldonadel gabrieldonadel commented Sep 6, 2024

Description

Update rnm-getting-started.md to recommend using react-native 0.75

Why

This documentation has been outdated for quite a while now and it's still recommending react-native 0.71. Now that 0.75 is out we should recommend that instead

Screenshots

N / A

Microsoft Reviewers: Open in CodeFlow

@gabrieldonadel gabrieldonadel requested a review from a team as a code owner September 6, 2024 19:58
@@ -5,7 +5,7 @@ title: Get Started with macOS

This guide will help you get started on setting up your very first React Native for macOS app.

>** Latest stable version available for React Native for macOS is 0.71**
>** Latest stable version available for React Native for macOS is 0.75**
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This won't show up on the website. You'll also need to edit (create) the 0.75 versioned doc of this file. You'll also probably want to fix the "old" new project commands (react-native@latest init) since that won't work anymore.

@jonthysell
Copy link
Contributor

+@Saadnajmi, can you take a look at this?

@Saadnajmi
Copy link
Collaborator

Hey @gabrieldonadel Thanks for the PR. For transparency: I often forget to update this repo as it's mostly outside of my view (partially evidenced by the fact it's in react-native-windows-samples). We (the macOS team) had been focused on getting 0.74 shipped and 0.75 shipped faster, which meant we missed a few of the steps we usually go back and do, like:

  • Update this repo
  • Update the upgrade-helper

I'm currently on vacation, but I'll be sure to take a look at both next week when I'm back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants