fix: configure next-release workflow to only run on next branch

- Change next-release.yaml to trigger on 'next' branch instead of 'main'
- Update next-release.ts to handle rn-new package versioning
- Ensure main branch only publishes to 'latest' tag via changesets
- Ensure next branch publishes to 'next' tag for development releases

Author: danstepanov

.github/workflows/next-release.yaml

@@ -2,7 +2,7 @@ name: Release Next
 on:
   push:
     branches:
-      - main
+      - next
 
 permissions:
   id-token: write
@@ -103,3 +103,6 @@ jobs:
           echo "//registry.npmjs.org/:_authToken=$NPM_TOKEN" >> ~/.npmrc
           cd ./cli
           npm publish --provenance --access public --ignore-scripts --tag next
+          cd ../packages/rn-new
+          bun run build
+          npm publish --provenance --access public --ignore-scripts --tag next

scripts/next-release.ts

@@ -24,6 +24,21 @@ async function createNextRelease() {
 
       const content = JSON.stringify(packageJson, null, '\t') + '\n';
       await Bun.write(process.cwd() + '/cli/package.json', content);
+
+      /**
+       * Also update the rn-new package.json with the same next version
+       */
+      const rnNewPackageJson = await Bun.file(process.cwd() + '/packages/rn-new/package.json').json();
+      const rnNewVersion = releasePlan.releases.find((release) => release.name === rnNewPackageJson.name)?.newVersion;
+
+      if (rnNewVersion) {
+        rnNewPackageJson.version = `${rnNewVersion}-next.${commitHash}`;
+        // Update the dependency to point to the next version of create-expo-stack
+        rnNewPackageJson.dependencies['create-expo-stack'] = `^${newNextVersion}-next.${commitHash}`;
+
+        const rnNewContent = JSON.stringify(rnNewPackageJson, null, '\t') + '\n';
+        await Bun.write(process.cwd() + '/packages/rn-new/package.json', rnNewContent);
+      }
     }
   } catch (error) {
     console.log(error);