Skip to content

chore: Back-merge release/8.9.1 into main#6055

Merged
antonis merged 5 commits intomainfrom
chore/back-merge-8.9.2
Apr 27, 2026
Merged

chore: Back-merge release/8.9.1 into main#6055
antonis merged 5 commits intomainfrom
chore/back-merge-8.9.2

Conversation

@antonis
Copy link
Copy Markdown
Contributor

@antonis antonis commented Apr 27, 2026

📢 Type of change

  • Bugfix
  • New feature
  • Enhancement
  • Refactoring
  • Other (back-merge)

📜 Description

Back-merges release/8.9.1 (which now contains the 8.9.2 release) into main. Brings the following onto main:

💡 Motivation and Context

8.9.2 was released from release/8.9.1 (since this was a hotfix on top of the 8.9.1 tag). Main needs the fix code, the new validate-tarball CI job, and the version bump so downstream releases continue from 8.9.2.

💚 How did you test it?

  • Ran git merge --no-ff origin/release/8.9.1 and resolved 6 file conflicts:
    • CHANGELOG.md: kept main's ## Unreleased block (8.10-bound entries) and inserted ## 8.9.2 between it and ## 8.9.1.
    • dev-packages/e2e-tests/package.json, samples/expo/package.json, samples/react-native-macos/package.json, samples/react-native/package.json: took @sentry/react-native: 8.9.2 from release branch, kept @sentry/core / @sentry/react at 10.50.0 from main (those are 8.10-bound bumps that should not regress to 10.49.0).
    • yarn.lock: regenerated with yarn install --mode=update-lockfile after package.json conflicts were resolved.
  • Verified post-merge state: packages/core/package.json is at 8.9.2, the validate-tarball CI job is present, .npmignore includes !scripts/eas-build-hook.js, build-tarball.sh has the chmod step.

📝 Checklist

  • I added tests to verify changes
  • No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled
  • I updated the docs if needed.
  • I updated the wizard if needed.
  • All tests passing
  • No breaking changes

🔮 Next steps

After merge, release/8.9.1 can be deleted (or kept around if further 8.9.x patches are anticipated). The next regular release will continue from main at 8.9.2.

🤖 Generated with Claude Code

antonis and others added 5 commits April 27, 2026 11:16
…ook (#6049)

* fix(core): Restore tarball script permissions and missing EAS build hook

The npm pack -> yarn pack switch in #6037 introduced two regressions:

1. yarn pack stores files with mode 0644. scripts/sentry-xcode.sh,
   invoked directly by Xcode's build phase, fails with "Permission
   denied" (#6047). Re-pack the tarball after yarn pack to restore 0755
   on shell scripts and bin entrypoints.

2. yarn pack does not auto-include files referenced from the bin field.
   scripts/eas-build-hook.js was never in the .npmignore allowlist, so
   the three sentry-eas-build-* bin commands silently stopped working
   in the tarball (#6048 follow-up). Add it to the allowlist.

Add a job_validate_tarball CI job that installs the produced tarball
into a fresh project and asserts script modes, bin links, post-install
executability, and that workspace:* specs were resolved.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* docs: Update changelog

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…6052)

The validate job ran `npm install <core tarball>` only. The published
core package.json declares `@sentry/expo-upload-sourcemaps` at the same
version as core (workspace:* is resolved at pack time). On a release
branch the bumped version is not on the npm registry yet, so npm tried
to fetch from registry and failed with ETARGET (e.g. when releasing
8.9.2: "No matching version found for @sentry/expo-upload-sourcemaps@8.9.2").

Install both tarballs together so the sister dep is satisfied from local.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…erge-8.9.2

# Conflicts:
#	CHANGELOG.md
#	dev-packages/e2e-tests/package.json
#	samples/expo/package.json
#	samples/react-native-macos/package.json
#	samples/react-native/package.json
#	yarn.lock
@antonis antonis added the ready-to-merge Triggers the full CI test suite label Apr 27, 2026
@antonis antonis marked this pull request as ready for review April 27, 2026 14:23
@antonis antonis merged commit b9a73af into main Apr 27, 2026
93 of 115 checks passed
@antonis antonis deleted the chore/back-merge-8.9.2 branch April 27, 2026 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ready-to-merge Triggers the full CI test suite

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants