Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions scripts/update-android-stubs.sh
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,9 @@ set-version)
echo "${content/${BASH_REMATCH[0]}/$newValue}" >$file

# Rebuild the stubs jar and JS types
cd ..
yarn build:replay-stubs || true
cd replay-stubs
echo "Building Stub"
./gradlew jar
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removed || true causes script failure on build errors

Medium Severity

The old command yarn build:replay-stubs || true intentionally suppressed build failures so the version-update workflow could continue even if the jar build failed. The new ./gradlew jar invocation drops the || true guard while the script uses set -euo pipefail, meaning any Gradle failure now aborts the entire version-update process (including when called from update-android.sh). If this strictness is intentional it's fine, but since the PR description only mentions removing yarn (not changing error handling), this looks like an accidental behavior change.

Fix in Cursor Fix in Web

;;
*)
echo "Unknown argument $1"
Expand Down
Loading