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

Release process #661

Merged
merged 4 commits into from
Jan 22, 2020
Merged

Conversation

mayurkale22
Copy link
Member

Which problem is this PR solving?

  • Update RELEASING.md


Merge the PR, and pull the changes locally (using the commands in the first step). Ensure that `chore: x.y.z release proposal` is the most recent commit.

## Publish all packages
Copy link
Member

Choose a reason for hiding this comment

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

Does this need to be a manual process? Why can we not use lerna publish for this?

Copy link
Member Author

Choose a reason for hiding this comment

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

So instead of npm publish on all the packages, just use lerna publish?

Copy link
Member

Choose a reason for hiding this comment

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

So instead of npm publish on all the packages, just use lerna publish?

I believe that lerna publish from-package should do the same at that point.

@codecov-io
Copy link

codecov-io commented Jan 3, 2020

Codecov Report

Merging #661 into master will increase coverage by 1.01%.
The diff coverage is 97.74%.

@@            Coverage Diff             @@
##           master     #661      +/-   ##
==========================================
+ Coverage   91.66%   92.67%   +1.01%     
==========================================
  Files         217      228      +11     
  Lines       10305    10361      +56     
  Branches      915      933      +18     
==========================================
+ Hits         9446     9602     +156     
+ Misses        859      759     -100
Impacted Files Coverage Δ
...ackages/opentelemetry-web/src/WebTracerRegistry.ts 100% <ø> (ø)
packages/opentelemetry-node/src/config.ts 100% <ø> (ø) ⬆️
...ges/opentelemetry-propagator-jaeger/src/version.ts 0% <ø> (ø)
...entelemetry-exporter-zipkin/test/transform.test.ts 100% <ø> (ø) ⬆️
packages/opentelemetry-web/test/WebTracer.test.ts 0% <0%> (ø) ⬆️
.../opentelemetry-core/test/metrics/NoopMeter.test.ts 97.29% <100%> (+0.07%) ⬆️
...metry-core/src/trace/instrumentation/BasePlugin.ts 86.84% <100%> (+0.73%) ⬆️
...ry-plugin-dns/test/functionals/dns-disable.test.ts 100% <100%> (ø) ⬆️
...telemetry-plugin-document-load/src/documentLoad.ts 97.95% <100%> (+0.02%) ⬆️
...s/opentelemetry-plugin-xml-http-request/src/xhr.ts 79.41% <100%> (-0.11%) ⬇️
... and 113 more


Merge the PR, and pull the changes locally (using the commands in the first step). Ensure that `chore: x.y.z release proposal` is the most recent commit.

## Publish all packages
Copy link
Member

Choose a reason for hiding this comment

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

So instead of npm publish on all the packages, just use lerna publish?

I believe that lerna publish from-package should do the same at that point.

@dyladan dyladan added the Merge:LGTM This PR is ready to be merged by a Maintainer (has enough valid approvals, successful build, etc.) label Jan 22, 2020
@mayurkale22 mayurkale22 merged commit 0ad90e7 into open-telemetry:master Jan 22, 2020
@mayurkale22 mayurkale22 deleted the RELEASING.md branch January 22, 2020 19:12
pichlermarc pushed a commit to dynatrace-oss-contrib/opentelemetry-js that referenced this pull request Dec 15, 2023
…ry#661)

Co-authored-by: William Armiros <54150514+willarmiros@users.noreply.github.com>
Co-authored-by: Daniel Dyla <dyladan@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
document Documentation-related Merge:LGTM This PR is ready to be merged by a Maintainer (has enough valid approvals, successful build, etc.)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants