chore(e2e): Link @sentry/bundler-plugins into the aws-serverless lambda test app - #23159
Merged
Merged
Conversation
…da test app Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
andreiborza
marked this pull request as ready for review
August 7, 2026 15:50
@sentry/bundler-plugins into the aws-serverless lambda test app@sentry/bundler-plugins into the aws-serverless lambda test app
nicohrubec
approved these changes
Aug 7, 2026
andreiborza
enabled auto-merge (squash)
August 7, 2026 15:53
Contributor
size-limit report 📦
|
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
2 participants
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.
What
The aws-serverless lambda test app now installs
@sentry/bundler-pluginsfrom the workspace instead of npm.bundler-pluginsto the list of packages the lambda functions link viafile:.Why
@sentry/nodedepends on@sentry/bundler-plugins, which the test app was resolving from the registry. On release branches that version isn't published yet, so the install failed withETARGETand the whole aws-serverless E2E job went down. This showed up onrelease/11.0.0-alpha.0.