ci: Unblock tag-triggered release workflows - #539
Merged
Merged
Conversation
Pin Node 24 in the Sentry Release workflow. Without it the runner's default npm 10 rejects the lockfile over an optional esbuild entry that npm 11 accepts, which has failed every Sentry release since v2.7.0. Raise the timeout of the live handler boundary probe to 120 seconds. On the macOS release runner the probes drive real xcodebuild and xcrun against missing projects and take about 45 seconds, while Linux CI finishes in a few seconds because the tools are absent. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
itaybre
marked this pull request as ready for review
September 23, 2026 20:11
commit: |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The v2.7.1 tag failed both tag-triggered workflows for reasons unrelated to the rename.
Sentry Release workflow
It does not pin a Node version, so the runner's default npm 10 rejects the lockfile over an optional esbuild entry under the nested vite package that npm 11 accepts. This has failed on every tag since v2.7.0. Pin Node 24 to match the CI and Release workflows.
Schema fixture test on macOS
The live handler boundary probe was added after v2.7.0, so the v2.7.1 tag was its first run on a macOS release runner. On macOS the probes drive real
xcodebuildandxcrunagainst missing projects and take about 45 seconds, while Linux CI finishes in seconds because the tools are absent. Raise its timeout to 120 seconds.🤖 Generated with Claude Code