chore: 0.3.3 release proposal

[mayurkale22]

Which problem is this PR solving?

• Weekly patch release

• Release draft note: https://github.com/open-telemetry/opentelemetry-js/releases/edit/untagged-f1f83ee5eb03f516352b https://github.com/open-telemetry/opentelemetry-js/releases/tag/untagged-00e5d05d8b9a54343719

• Total 79 files updated:

  30 packages (version.ts + package.json) = 60
  test-utils package (only package.json) = 1
  13 examples (package.json) = 13
  3 getting-started (package.json) = 3
  1 lerna.json = 1
  1 package.json = 1
  

• Examples in getting-started/ guide are out-of-date(Update getting-started guide based on TracerRegistry #682), hence didn't update package version there. Done.

• Blocked on feat(TracerRegistry): set default name when nothing is provided #681

[codecov-io]

Codecov Report

Merging #683 into master will decrease coverage by 1.59%.
The diff coverage is 41.66%.

@@           Coverage Diff            @@
##           master    #683     +/-   ##
========================================
- Coverage    92.7%   91.1%   -1.6%     
========================================
  Files         228     225      -3     
  Lines       10425   10462     +37     
  Branches      939     966     +27     
========================================
- Hits         9664    9531    -133     
- Misses        761     931    +170

Impacted Files	Coverage Δ
packages/opentelemetry-plugin-dns/src/version.ts	100% <ø> (ø)	⬆️
packages/opentelemetry-plugin-http/src/version.ts	100% <ø> (ø)	⬆️
...in-postgres/opentelemetry-plugin-pg/src/version.ts	100% <ø> (ø)	⬆️
packages/opentelemetry-plugin-grpc/src/version.ts	100% <ø> (ø)	⬆️
...ges/opentelemetry-scope-async-hooks/src/version.ts	0% <0%> (ø)	⬆️
packages/opentelemetry-plugin-https/src/version.ts	0% <0%> (ø)	⬆️
...kages/opentelemetry-exporter-jaeger/src/version.ts	0% <0%> (ø)	⬆️
packages/opentelemetry-tracing/src/version.ts	0% <0%> (ø)	⬆️
packages/opentelemetry-web/src/version.ts	0% <0%> (ø)	⬆️
packages/opentelemetry-metrics/src/version.ts	0% <0%> (ø)	⬆️
... and 56 more

[obecny]

lgtm

[dyladan]

The build failure is a SIGHUP received during the bootstrap phase of the build. Is it possible we are running out of memory on our build node?

[mayurkale22]

Any idea why build is failing for node8 job?

[obecny]

maybe this can help
https://discuss.circleci.com/t/builds-getting-killed-with-vague-message-received-signal-killed/10214/8
If I understand correctly basically try to add cmd: ["/bin/bash"] to config.yml
Haven't tried that though

  node8:
    docker:
      - image: node:8
        environment: *node_test_env
        cmd: ["/bin/bash"]
      - *postgres_service
      - *mysql_service
      - *redis_service
      - *mongo_service
    <<: *node_unit_tests

[mayurkale22]

Removed examples/* (added by mistake, earlier) from lerna and build is passed. @dyladan thanks for noticing this :)