Skip to content

Conversation

@pichlermarc
Copy link
Member

Which problem is this PR solving?

In #5946 we slightly changed the process of publishing to NPM. This PR updates the documentation with the missing steps.

@pichlermarc pichlermarc requested a review from a team as a code owner October 21, 2025 12:07
@codecov
Copy link

codecov bot commented Oct 21, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 95.14%. Comparing base (3fc7170) to head (3a4cf24).

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #6033      +/-   ##
==========================================
- Coverage   95.15%   95.14%   -0.02%     
==========================================
  Files         316      316              
  Lines        9166     9166              
  Branches     2023     2023              
==========================================
- Hits         8722     8721       -1     
- Misses        444      445       +1     

see 1 file with indirect coverage changes

🚀 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.

> [!NOTE]
> You can skip this step if the `publish-to-npm` workflow completed successfully.
- New packages that have never been published before cannot be published this way - contact an `@opentelemetry` org Admin to publish them manually.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is intentionally left vague - it does not happen too often and I'll add info/screenshots the next time I have to do it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants