From e854ce3b1551a4ac97012336c2e2076ab0cc0636 Mon Sep 17 00:00:00 2001 From: Jack Pope Date: Thu, 12 Dec 2024 14:11:24 -0500 Subject: [PATCH] Fix canary version strings (#31721) We're still publishing RCs and creating canary version strings using the RC naming convention. Setting the `canaryChannelLabel` back to canary fixes the version names and tags after the 19 stable release. --- ReactVersions.js | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ReactVersions.js b/ReactVersions.js index e4ce043171f79..7385671dcc626 100644 --- a/ReactVersions.js +++ b/ReactVersions.js @@ -26,11 +26,11 @@ const ReactVersion = '19.1.0'; // // It only affects the label used in the version string. To customize the // npm dist tags used during publish, refer to .github/workflows/runtime_prereleases_*.yml. -const canaryChannelLabel = 'rc'; +const canaryChannelLabel = 'canary'; // If the canaryChannelLabel is "rc", the build pipeline will use this to build // an RC version of the packages. -const rcNumber = 1; +const rcNumber = 0; const stablePackages = { 'eslint-plugin-react-hooks': '5.2.0',