Skip to content
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(deps): update otel group #3068

Merged
merged 3 commits into from
Jan 8, 2024
Merged

chore(deps): update otel group #3068

merged 3 commits into from
Jan 8, 2024

Conversation

ramin
Copy link
Contributor

@ramin ramin commented Jan 3, 2024

reduced myself to fixing dependabot's attempts to upgrade us at #3055 was not working quite right

@ramin ramin added the kind:deps Pull requests that update a dependency file label Jan 3, 2024
@codecov-commenter
Copy link

codecov-commenter commented Jan 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (45e1847) 51.34% compared to head (a24e2db) 51.29%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #3068      +/-   ##
==========================================
- Coverage   51.34%   51.29%   -0.05%     
==========================================
  Files         177      177              
  Lines       11151    11151              
==========================================
- Hits         5725     5720       -5     
- Misses       4928     4932       +4     
- Partials      498      499       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@walldiss
Copy link
Member

walldiss commented Jan 3, 2024

I think it didn't initially add

github.com/pyroscope-io/otel-profiling-go

Because it is not in actual otel group, but rather an pyroscope intagration, that lives in pyroscope repo. Does otel group depend on pyroscope pkg? Do we need it in same group?

@walldiss
Copy link
Member

walldiss commented Jan 3, 2024

This bump unblocks this one
#2470
It brings update to otel, that allows long waited specified bundaries for histogram metrics.

@ramin ramin enabled auto-merge (squash) January 8, 2024 11:51
@ramin ramin merged commit 1afe0a1 into main Jan 8, 2024
15 of 17 checks passed
@ramin ramin deleted the chore/ramin/update-otel branch January 8, 2024 11:56
distractedm1nd pushed a commit that referenced this pull request Jan 10, 2024
<!--
Thank you for submitting a pull request!

Please make sure you have reviewed our contributors guide before
submitting your
first PR.

Please ensure you've addressed or included references to any related
issues.

Tips:
- Use keywords like "closes" or "fixes" followed by an issue number to
automatically close related issues when the PR is merged (e.g., "closes
#123" or "fixes #123").
- Describe the changes made in the PR.
- Ensure the PR has one of the required tags (kind:fix, kind:misc,
kind:break!, kind:refactor, kind:feat, kind:deps, kind:docs, kind:ci,
kind:chore, kind:testing)

-->

reduced myself to fixing dependabot's attempts to upgrade us at
#3055 was not working
quite right
renaynay pushed a commit to renaynay/celestia-node that referenced this pull request Jan 15, 2024
<!--
Thank you for submitting a pull request!

Please make sure you have reviewed our contributors guide before
submitting your
first PR.

Please ensure you've addressed or included references to any related
issues.

Tips:
- Use keywords like "closes" or "fixes" followed by an issue number to
automatically close related issues when the PR is merged (e.g., "closes
#123" or "fixes #123").
- Describe the changes made in the PR.
- Ensure the PR has one of the required tags (kind:fix, kind:misc,
kind:break!, kind:refactor, kind:feat, kind:deps, kind:docs, kind:ci,
kind:chore, kind:testing)

-->

reduced myself to fixing dependabot's attempts to upgrade us at
celestiaorg#3055 was not working
quite right
renaynay pushed a commit to renaynay/celestia-node that referenced this pull request Jan 15, 2024
<!--
Thank you for submitting a pull request!

Please make sure you have reviewed our contributors guide before
submitting your
first PR.

Please ensure you've addressed or included references to any related
issues.

Tips:
- Use keywords like "closes" or "fixes" followed by an issue number to
automatically close related issues when the PR is merged (e.g., "closes
#123" or "fixes #123").
- Describe the changes made in the PR.
- Ensure the PR has one of the required tags (kind:fix, kind:misc,
kind:break!, kind:refactor, kind:feat, kind:deps, kind:docs, kind:ci,
kind:chore, kind:testing)

-->

reduced myself to fixing dependabot's attempts to upgrade us at
celestiaorg#3055 was not working
quite right
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind:deps Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants