Skip to content

[chore][code-scanning] Upgrade golang.org/x/crypto used by TA #6179

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

Merged
merged 1 commit into from
Apr 30, 2025

Conversation

pjanotti
Copy link
Contributor

@pjanotti pjanotti requested review from a team as code owners April 30, 2025 19:16
Copy link

codecov bot commented Apr 30, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 44.46%. Comparing base (7529376) to head (bca6dcd).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6179      +/-   ##
==========================================
- Coverage   44.47%   44.46%   -0.01%     
==========================================
  Files         390      390              
  Lines       27014    27014              
==========================================
- Hits        12015    12013       -2     
- Misses      14158    14159       +1     
- Partials      841      842       +1     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@pjanotti pjanotti merged commit 1aeaea7 into signalfx:main Apr 30, 2025
70 checks passed
@pjanotti pjanotti deleted the upgrade-crypto-pkg-for-ta branch April 30, 2025 20:18
@github-actions github-actions bot locked and limited conversation to collaborators Apr 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants