use build:tarball everywhere

Author: mydea

.github/workflows/build.yml

@@ -344,7 +344,7 @@ jobs:
           path: ${{ env.CACHED_BUILD_PATHS }}
           key: ${{ env.BUILD_CACHE_KEY }}
       - name: Pack
-        run: yarn build:npm
+        run: yarn build:tarball
       - name: Archive artifacts
         uses: actions/[email protected]
         with:

docs/new-sdk-release-checklist.md

@@ -21,7 +21,7 @@ This page serves as a checklist of what to do when releasing a new SDK for the f
 - [ ]  Make sure that the `LICENSE` file exists and has the correct license (We default to the `MIT` license)
     - [ ]  Also check, that the same license is mentioned in `package.json`
 
-- [ ]  Make sure that the tarball (`yarn build:npm`) has all the necessary contents
+- [ ]  Make sure that the tarball (`yarn build:tarball`) has all the necessary contents
 
     For basic SDKs, this means that the tarball has at least these files:
 

packages/e2e-tests/publish-packages.ts

@@ -6,7 +6,7 @@ import * as path from 'path';
 const repositoryRoot = path.resolve(__dirname, '../..');
 
 // Create tarballs
-childProcess.execSync('yarn build:npm', { encoding: 'utf8', cwd: repositoryRoot, stdio: 'inherit' });
+childProcess.execSync('yarn build:tarball', { encoding: 'utf8', cwd: repositoryRoot, stdio: 'inherit' });
 
 // Get absolute paths of all the packages we want to publish to the fake registry
 const packageTarballPaths = glob.sync('packages/*/sentry-*.tgz', {

packages/replay/workflows/build.yml

@@ -26,7 +26,7 @@ jobs:
           yarn build
 
       - run: |
-          yarn build:npm
+          yarn build:tarball
 
       - uses: actions/[email protected]
         with: