chore: move aws lambda types dependency to root #2001
Merged
Conversation
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
wpessers
force-pushed
the
chore/define-aws-lambda-types-dependency-in-root
branch
2 times, most recently
from
d5dc745 to
345adfc
Compare
wpessers
force-pushed
the
chore/define-aws-lambda-types-dependency-in-root
branch
from
345adfc to
4451593
Compare
tylerbenson
approved these changes
Oct 22, 2025
serkan-ozal
approved these changes
Oct 22, 2025
adamantal
pushed a commit
to adamantal/opentelemetry-lambda
that referenced
this pull request
Nov 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Moved the
@types/aws-lambdadependency to our root package.json to be used in both workspaces. This should fix the conflict with the transitive dependency from the lambda instrumentation dependency.