You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/blog/2019-10-22-react-release-channels.md
+7-7
Original file line number
Diff line number
Diff line change
@@ -13,7 +13,7 @@ Because the source of truth for React is our [public GitHub repository](https://
13
13
14
14
We would like to make it even easier for developers to test prerelease builds of React, so we're formalizing our process with three separate release channels.
15
15
16
-
## Release Channels
16
+
## Release Channels {#release-channels}
17
17
18
18
> The information in this post is also available on our [Release Channels](/docs/release-channels.html) page. We will update that document whenever there are changes to our release process.
19
19
@@ -29,15 +29,15 @@ All releases are published to npm, but only Latest uses [semantic versioning](/d
29
29
30
30
By publishing prereleases to the same registry that we use for stable releases, we are able to take advantage of the many tools that support the npm workflow, like [unpkg](https://unpkg.com) and [CodeSandbox](https://codesandbox.io).
31
31
32
-
### Latest Channel
32
+
### Latest Channel {#latest-channel}
33
33
34
34
Latest is the channel used for stable React releases. It corresponds to the `latest` tag on npm. It is the recommended channel for all React apps that are shipped to real users.
35
35
36
36
**If you're not sure which channel you should use, it's Latest.** If you're a React developer, this is what you're already using.
37
37
38
38
You can expect updates to Latest to be extremely stable. Versions follow the semantic versioning scheme. Learn more about our commitment to stability and incremental migration in our [versioning policy](/docs/faq-versioning.html).
39
39
40
-
### Next Channel
40
+
### Next Channel {#next-channel}
41
41
42
42
The Next channel is a prerelease channel that tracks the master branch of the React repository. We use prereleases in the Next channel as release candidates for the Latest channel. You can think of Next as a superset of Latest that is updated more frequently.
43
43
@@ -47,7 +47,7 @@ The degree of change between the most recent Next release and the most recent La
47
47
48
48
Releases in Next are published with the `next` tag on npm. Versions are generated from a hash of the build's contents, e.g. `0.0.0-1022ee0ec`.
49
49
50
-
#### Using the Next Channel for Integration Testing
50
+
#### Using the Next Channel for Integration Testing {#using-the-next-channel-for-integration-testing}
51
51
52
52
The Next channel is designed to support integration testing between React and other projects.
53
53
@@ -73,7 +73,7 @@ If you're the author of a third party React framework, library, developer tool,
73
73
74
74
A project that uses this workflow is Next.js. (No pun intended! Seriously!) You can refer to their [CircleCI configuration](https://github.com/zeit/next.js/blob/c0a1c0f93966fe33edd93fb53e5fafb0dcd80a9e/.circleci/config.yml) as an example.
75
75
76
-
### Experimental Channel
76
+
### Experimental Channel {#experimental-channel}
77
77
78
78
Like Next, the Experimental channel is a prerelease channel that tracks the master branch of the React repository. Unlike Next, Experimental releases include additional features and APIs that are not ready for wider release.
79
79
@@ -83,15 +83,15 @@ Experimental releases may be significantly different than releases to Next and L
83
83
84
84
Releases in Experimental are published with the `experimental` tag on npm. Versions are generated from a hash of the build's contents, e.g. `0.0.0-experimental-1022ee0ec`.
85
85
86
-
#### What Goes Into an Experimental Release?
86
+
#### What Goes Into an Experimental Release? {#what-goes-into-an-experimental-release}
87
87
88
88
Experimental features are ones that are not ready to be released to the wider public, and may change drastically before they are finalized. Some experiments may never be finalized -- the reason we have experiments is to test the viability of proposed changes.
89
89
90
90
For example, if the Experimental channel had existed when we announced Hooks, we would have released Hooks to the Experimental channel weeks before they were available in Latest.
91
91
92
92
You may find it valuable to run integration tests against Experimental. This is up to you. However, be advised that Experimental is even less stable than Next. **We do not guarantee any stability between Experimental releases.**
93
93
94
-
#### How Can I Learn More About Experimental Features?
94
+
#### How Can I Learn More About Experimental Features? {#how-can-i-learn-more-about-experimental-features}
95
95
96
96
Experimental features may or may not be documented. Usually, experiments aren't documented until they are close to shipping in Next or Stable.
0 commit comments