-
Notifications
You must be signed in to change notification settings - Fork 804
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(instrumentation): remove accidental devDep on api-logs #4627
Merged
pichlermarc
merged 2 commits into
open-telemetry:main
from
trentm:tm-package-lock-deps-fixes
Apr 11, 2024
Merged
chore(instrumentation): remove accidental devDep on api-logs #4627
pichlermarc
merged 2 commits into
open-telemetry:main
from
trentm:tm-package-lock-deps-fixes
Apr 11, 2024
Conversation
This file contains 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
This package accidentally got a dep and devDep on api-logs, at different versions. The result was it being pinned at the older version in package-lock.
Before:
After:
|
Flarna
approved these changes
Apr 11, 2024
pichlermarc
approved these changes
Apr 11, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, thanks for removing this 👍
legalimpurity
pushed a commit
to legalimpurity/opentelemetry-js
that referenced
this pull request
Apr 26, 2024
…lemetry#4627) This package accidentally got a dep and devDep on api-logs, at different versions. The result was it being pinned at the older version in package-lock. Co-authored-by: Marc Pichler <marc.pichler@dynatrace.com>
Zirak
pushed a commit
to Zirak/opentelemetry-js
that referenced
this pull request
Sep 14, 2024
…lemetry#4627) This package accidentally got a dep and devDep on api-logs, at different versions. The result was it being pinned at the older version in package-lock. Co-authored-by: Marc Pichler <marc.pichler@dynatrace.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This package accidentally got a dep and devDep on api-logs, at
different versions. The result was it being pinned at the older
version in package-lock.
@pichlermarc I am still trying to understand why the huge package-lock diff in #4621. While playing around I noticed this buglet. I'm not sure it was causing any bugs, but I think it meant that local testing of this
instrumentation
package (i.e. when installing with package-lock) would have been using the older api-logs./me gives mean eyes to
npm
that blithely doesn't complain when there are incompatible entries in "dependencies" and "devDependencies".