From 0f6eb7889d3455a2e0a79d73676d23ac3c80213c Mon Sep 17 00:00:00 2001 From: Andrea Bueide Date: Fri, 24 Jul 2026 16:21:13 -0500 Subject: [PATCH] ci: remove the post-release Update Apps step Traced its origin back to a local devbox maintenance script (update-apps, meant for a maintainer to manually refresh the example app's lockfile) that got wired into the production release job at some point. As a CI step it never made sense: it runs after the actual npm publish, so it can't gate release correctness, and nothing here commits or pushes the "updated" lockfiles back - the runner is ephemeral, so the whole step is a no-op with no lasting effect except surfacing unrelated curation-block noise (examples/AnalyticsReactNativeExample is a standalone yarn project outside the root workspace, so it isn't covered by any of this session's resolutions fixes) that makes a successful release look broken. --- .github/workflows/release.yml | 5 ----- 1 file changed, 5 deletions(-) diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 084914cfc..9eee383b5 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -186,8 +186,3 @@ jobs: env: GH_TOKEN: ${{ github.token }} NPM_CONFIG_IGNORE_SCRIPTS: 'true' - - - name: Update Apps - run: | - yarn install --no-immutable - yarn --cwd examples/AnalyticsReactNativeExample install --no-immutable