[blog] Announcement of react-native-git-upgrade #11263

ncuillery · 2016-12-02T06:45:47Z

Ping @mkonicek

mkonicek · 2016-12-02T15:41:40Z

@facebook-github-bot import

facebook-github-bot · 2016-12-02T15:42:29Z

@mkonicek has imported this pull request. If you are a Facebook employee, you can view this diff on Phabricator.

mkonicek · 2016-12-02T18:49:38Z

Hi Nicolas, I've done a pass at the blogpost:

Added an introduction to the current state of upgrading, inspired by your original blogpost, I think this can be useful to se the context so everyone knows what exact problem react-native-git-upgrade is solving
Moved the Usage section closer to the beginning as this will likely be the most interesting section to people (copy&paste ftw), after which they can decide to immediately go and try it, or continue reading
Made wording and grammar changes

mkonicek · 2016-12-02T18:59:30Z

blog/2016-12-05-easy-upgrades-processed-by-git.md


-The standalone package is a temporary situation for a few months, it would probably never see the _1.0.0_ release: when most users will have migrated their projects to the _post-Yeoman era_ using this package, it will replace the actual `react-native upgrade` and the global package `react-native-git-upgrade` will be deprecated.


Rather than talk about deprecation of this new tool when it's announced, mention how this new hotness is going to be integrated the React Native CLI.

(Positive wording)

mkonicek · 2016-12-02T19:00:31Z

blog/2016-12-05-easy-upgrades-processed-by-git.md


-As a conclusion, I would say, enjoy the feature and feel free [to suggest improvements, report issues and send pull requests](https://github.com/facebook/react-native/issues). Each user has its own runtime environment, each React Native project is different, so we need you to make this process completely reliable and universal !


Changed the wording slightly to specify what we mean by "User has their own runtime environment".

mkonicek · 2016-12-02T19:01:06Z

blog/2016-12-05-easy-upgrades-processed-by-git.md


-## Why a separated package ?


Kept this, just changed the wording.

mkonicek · 2016-12-02T19:02:17Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+$ react-native-git-upgrade 0.38.0
+```
+
+> Note: Do **not** run 'npm install' to install a new version of `react-native`. The tool needs to be able to compare the old and new project template to work correctly. Simply run it inside your app folder as shown above, while still on the old version.


Made this a bit shorter without going to the details (leaving details for the How it works section).

mkonicek · 2016-12-02T19:03:24Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+  a) overwrite this and all others
+  x) abort
+  d) show the differences between the old and the new
+  h) Help, list all options


Explain what problem react-native-git-upgrade solves using an example, inspired by the original blogpost: https://medium.com/@ncuillery/easier-react-native-upgrades-with-rn-diff-5020b5c3de2d#.wuv996x14

👍

I think we could have a better looking with a colorful screenshot rather than the code snippet. What do you think ?

mkonicek · 2016-12-02T19:03:55Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+
+None of the options is what we want. By overwriting the file we lose changes we've made locally. What if we tried to resolve the conflicts automatically instead?
+
+Today I am proud to introduce a new tool which makes upgrading easier. The tool is called `react-native-git-upgrade` and uses Git behind the scenes.


Leave out the part Git is the most popular. It probably is but I'm not 100% sure and it's not important in this blogpost.

ncuillery · 2016-12-03T13:22:34Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+category: announcements
+---
+
+Upgrading to each new version of React Native has been painful. You might have seen something like this before:


I've noted that the first sentence is actually the teaser seen on the home page. That's why I went with a long sentence introducing the blog post and encouraging people to read it:

Each release of React Native may come with changes inside the iOS and Android sub-projects that you have to report in your project. This synchronisation has always been a major pain point because of the poor changes detection within your source files. Today, I'm proud to announce a new upgrading process relying on the most popular version control system: Git.

At the current time, the home page looks like this:

edvinerikson · 2016-12-03T13:26:48Z

seems like this has been published already. is the date wrong or is it mistakenly published?
https://facebook.github.io/react-native/blog/2016/12/05/easy-upgrades-processed-by-git.html

ncuillery · 2016-12-03T13:32:40Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+
+## Usage
+
+Requirements: Git has to be available in the `PATH`. Your project doesn't have to be managed by Git.


Suggestion: Quote character to wrap this in a orange block ?

Requirement should be singular, this is the only one 💪

Preview (with "requirement:" bold):

ncuillery · 2016-12-03T13:34:04Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+
+![](/react-native/blog/img/git-upgrade-output.png)
+
+You can also run `react-native-git-upgrade` with no arguments to upgrade to the latest version.


no argument

singular

The word after "no" doesn't always have to be singular. Google returns a similar number of results for "no argument" and "no arguments".

ncuillery · 2016-12-03T14:07:23Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+
+React Native comes with a global CLI (the [react-native-cli](https://www.npmjs.com/package/react-native-cli) package) which delegates commands to the local CLI embedded in the `node_modules/react-native/local-cli` directory.
+
+As we mentioned above, the process has to be started from your current React Native version. If we had embedded the implementation in the local-cli, you wouldn't have been able to enjoy this feature until when using old versions of React Native. For example, you wouldn't be able to upgrade from 0.29.2 to 0.38.0 if this new upgrade code was only released in 0.38.0.


you wouldn't have been able to enjoy this feature until when using old versions of React Native

I'm not 100% sure but... I understood the opposite because of "until". Shouldn't we say "you wouldn't have been able to enjoy this feature when using old versions of React Native" ?

Good catch, thanks!

ncuillery · 2016-12-03T14:15:05Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+
+## Looking ahead
+
+The logic behind `react-native-git-upgrade` described above is going to power the standard `react-native upgrade` starting with React Native version 0.40.0.


I didn't know that \o/ 🎉

Oops, sorry I didn't explain that clearly!

ncuillery · 2016-12-03T14:19:41Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+
+The logic behind `react-native-git-upgrade` described above is going to power the standard `react-native upgrade` starting with React Native version 0.40.0.
+
+This means that if you are upgrading __from version 0.40.0 or higher__, you will be able to simply run `react-native upgrade` in your project without having to install anything globally. The `react-native-git-upgrade` is provided so anyone can have this improved experience now while using an older version of React Native.


Suggestion:

so anyone can have this improved experience now while using an older version of React Native.

👉 so anyone can enjoy this improved experience from today while using an older version of React Native.

Nice! Thank you.

ncuillery · 2016-12-03T14:26:08Z

blog/2016-12-05-easy-upgrades-processed-by-git.md

+
+## Please try it out and provide feedback
+
+As a conclusion, I would say, enjoy the feature and feel free [to suggest improvements, report issues](https://github.com/facebook/react-native/issues) and especially [send pull requests](https://github.com/facebook/react-native/pulls). There are many configurations of operating system and Node version, each React Native project is different, and we need your feedback to make this work well for everyone.


"to make this working well for everyone" ?

I believe "make sth work" is more common?
http://www.phrasemix.com/phrases/make-something-work

It sounds strange to me at first, because I asked myself if "work" was a noun or a verb... but it is not really important, move forward with "make this work". 👍

Summary: Ping mkonicek ![fireshot capture 4 - easy upgrades relying on git_ - http___localhost_8079_react-native_](https://cloud.githubusercontent.com/assets/4425455/20825225/fe93bcb2-b862-11e6-8f0d-123ef2c9071f.png) Closes facebook#11263 Differential Revision: D4265603 Pulled By: mkonicek fbshipit-source-id: 8e496f0d76536744f2b25848a974f240bb5fae3e

Summary: Ping mkonicek ![fireshot capture 4 - easy upgrades relying on git_ - http___localhost_8079_react-native_](https://cloud.githubusercontent.com/assets/4425455/20825225/fe93bcb2-b862-11e6-8f0d-123ef2c9071f.png) Closes #11263 Differential Revision: D4265603 Pulled By: mkonicek fbshipit-source-id: 8e496f0d76536744f2b25848a974f240bb5fae3e

Summary: Ping mkonicek ![fireshot capture 4 - easy upgrades relying on git_ - http___localhost_8079_react-native_](https://cloud.githubusercontent.com/assets/4425455/20825225/fe93bcb2-b862-11e6-8f0d-123ef2c9071f.png) Closes facebook#11263 Differential Revision: D4265603 Pulled By: mkonicek fbshipit-source-id: 8e496f0d76536744f2b25848a974f240bb5fae3e

Announcement of react-native-git-upgrade

02db5ff

facebook-github-bot added GH Review: review-needed CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Import Started This pull request has been imported. This does not imply the PR has been approved. labels Dec 2, 2016

Restructure, wording

4e313bf

mkonicek reviewed Dec 2, 2016

View reviewed changes

facebook-github-bot closed this in 9c5efa3 Dec 2, 2016

ncuillery commented Dec 3, 2016

View reviewed changes

koubaabdellah mentioned this pull request Nov 27, 2023

[Snyk] Fix for 1 vulnerabilities koubaabdellah/react-native#13

Open

koubaabdellah mentioned this pull request Jan 8, 2024

[Snyk] Security upgrade jest from 26.6.3 to 27.0.0 koubaabdellah/react-native#21

Open

This was referenced May 13, 2024

[Snyk] Fix for 2 vulnerabilities koubaabdellah/react-native#27

Open

[Snyk] Security upgrade jest from 26.6.3 to 27.0.0 koubaabdellah/react-native#31

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[blog] Announcement of react-native-git-upgrade #11263

[blog] Announcement of react-native-git-upgrade #11263

ncuillery commented Dec 2, 2016

mkonicek commented Dec 2, 2016

facebook-github-bot commented Dec 2, 2016

mkonicek commented Dec 2, 2016 •

edited

Loading

mkonicek Dec 2, 2016

mkonicek Dec 2, 2016

mkonicek Dec 2, 2016

mkonicek Dec 2, 2016

mkonicek Dec 2, 2016

ncuillery Dec 3, 2016

mkonicek Dec 2, 2016

ncuillery Dec 3, 2016

edvinerikson commented Dec 3, 2016

ncuillery Dec 3, 2016

ncuillery Dec 3, 2016

mkonicek Dec 5, 2016

ncuillery Dec 3, 2016 •

edited

Loading

mkonicek Dec 5, 2016

ncuillery Dec 3, 2016

mkonicek Dec 5, 2016

ncuillery Dec 3, 2016

mkonicek Dec 5, 2016

ncuillery Dec 3, 2016

mkonicek Dec 5, 2016

ncuillery Dec 5, 2016


		The standalone package is a temporary situation for a few months, it would probably never see the _1.0.0_ release: when most users will have migrated their projects to the _post-Yeoman era_ using this package, it will replace the actual `react-native upgrade` and the global package `react-native-git-upgrade` will be deprecated.


		As a conclusion, I would say, enjoy the feature and feel free [to suggest improvements, report issues and send pull requests](https://github.com/facebook/react-native/issues). Each user has its own runtime environment, each React Native project is different, so we need you to make this process completely reliable and universal !


		None of the options is what we want. By overwriting the file we lose changes we've made locally. What if we tried to resolve the conflicts automatically instead?

		Today I am proud to introduce a new tool which makes upgrading easier. The tool is called `react-native-git-upgrade` and uses Git behind the scenes.


		## Usage

		Requirements: Git has to be available in the `PATH`. Your project doesn't have to be managed by Git.


		![](/react-native/blog/img/git-upgrade-output.png)

		You can also run `react-native-git-upgrade` with no arguments to upgrade to the latest version.


		React Native comes with a global CLI (the [react-native-cli](https://www.npmjs.com/package/react-native-cli) package) which delegates commands to the local CLI embedded in the `node_modules/react-native/local-cli` directory.

		As we mentioned above, the process has to be started from your current React Native version. If we had embedded the implementation in the local-cli, you wouldn't have been able to enjoy this feature until when using old versions of React Native. For example, you wouldn't be able to upgrade from 0.29.2 to 0.38.0 if this new upgrade code was only released in 0.38.0.


		## Looking ahead

		The logic behind `react-native-git-upgrade` described above is going to power the standard `react-native upgrade` starting with React Native version 0.40.0.


		The logic behind `react-native-git-upgrade` described above is going to power the standard `react-native upgrade` starting with React Native version 0.40.0.

		This means that if you are upgrading __from version 0.40.0 or higher__, you will be able to simply run `react-native upgrade` in your project without having to install anything globally. The `react-native-git-upgrade` is provided so anyone can have this improved experience now while using an older version of React Native.


		## Please try it out and provide feedback

		As a conclusion, I would say, enjoy the feature and feel free [to suggest improvements, report issues](https://github.com/facebook/react-native/issues) and especially [send pull requests](https://github.com/facebook/react-native/pulls). There are many configurations of operating system and Node version, each React Native project is different, and we need your feedback to make this work well for everyone.

[blog] Announcement of react-native-git-upgrade #11263

[blog] Announcement of react-native-git-upgrade #11263

Conversation

ncuillery commented Dec 2, 2016

mkonicek commented Dec 2, 2016

facebook-github-bot commented Dec 2, 2016

mkonicek commented Dec 2, 2016 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

edvinerikson commented Dec 3, 2016

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

ncuillery Dec 3, 2016 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

mkonicek commented Dec 2, 2016 •

edited

Loading

ncuillery Dec 3, 2016 •

edited

Loading