Merge branch 'main' into bring-back-browser-extension

.github/component_owners.yml

@@ -3,9 +3,12 @@ components:
   detectors/node/opentelemetry-resource-detector-alibaba-cloud:
     - legendecas
   detectors/node/opentelemetry-resource-detector-aws:
-    - willarmiros
-  detectors/node/opentelemetry-resource-detector-docker:
+    - carolabadeer
+  detectors/node/opentelemetry-resource-detector-container:
     - abhee11
+  detectors/node/opentelemetry-resource-detector-instana:
+    - basti1302
+    - kirrg001
   metapackages/auto-instrumentations-node:
     - obecny
   metapackages/auto-instrumentations-web:
@@ -15,7 +18,9 @@ components:
   packages/opentelemetry-host-metrics:
     - legendecas
   packages/opentelemetry-id-generator-aws-xray:
-    - willarmiros
+    - carolabadeer
+  packages/opentelemetry-redis-common:
+    - haddasbronfman
   plugins/node/instrumentation-amqplib:
     - blumamir
   plugins/node/instrumentation-dataloader:
@@ -25,9 +30,9 @@ components:
   plugins/node/instrumentation-tedious:
     - rauno56
   plugins/node/opentelemetry-instrumentation-aws-lambda:
-    - willarmiros
+    - carolabadeer
   plugins/node/opentelemetry-instrumentation-aws-sdk:
-    - willarmiros
+    - carolabadeer
     - blumamir
   plugins/node/opentelemetry-instrumentation-generic-pool:
     - rauno56
@@ -46,6 +51,8 @@ components:
     - osherv
   plugins/node/opentelemetry-instrumentation-mongoose:
     - blumamir
+  plugins/node/opentelemetry-instrumentation-mysql:
+    - haddasbronfman
   plugins/node/opentelemetry-instrumentation-nestjs-core:
     - rauno56
   plugins/node/opentelemetry-instrumentation-redis:
@@ -58,6 +65,9 @@ components:
     - rauno56
   plugins/node/opentelemetry-instrumentation-pg:
     - rauno56
+  plugins/node/opentelemetry-instrumentation-socket.io:
+    - mottibec
+    - rauno56
   plugins/web/opentelemetry-instrumentation-document-load:
     - obecny
   plugins/web/opentelemetry-instrumentation-long-task:
@@ -66,7 +76,7 @@ components:
   plugins/web/opentelemetry-instrumentation-user-interaction:
     - obecny
   propagators/opentelemetry-propagator-aws-xray:
-    - willarmiros
+    - carolabadeer
   propagators/opentelemetry-propagator-instana:
     - basti1302
     - kirrg001

.github/workflows/close-stale.yml

@@ -7,7 +7,7 @@ jobs:
   stale:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@v6
+      - uses: actions/stale@v8
         with:
           days-before-stale: 60
           days-before-close: 14

.github/workflows/release-please.yml

@@ -8,13 +8,6 @@ jobs:
   release-please:
     runs-on: ubuntu-latest
     steps:
-      - uses: google-github-actions/release-please-action@v3
-        id: release
-        with:
-          command: manifest
-          token: ${{secrets.RELEASE_PR_TOKEN}}
-          default-branch: main
-
       # The logic below handles the npm publication:
       - name: Checkout Repository
         uses: actions/checkout@v3
@@ -46,6 +39,13 @@ jobs:
           npm install
           npx lerna bootstrap --no-ci
 
+      - uses: google-github-actions/release-please-action@v3
+        id: release
+        with:
+          command: manifest
+          token: ${{secrets.RELEASE_PR_TOKEN}}
+          default-branch: main
+
       # Release Please has already incremented versions and published tags, so we just
       # need to publish all unpublished versions to npm here
       # See: https://github.com/lerna/lerna/tree/main/commands/publish#bump-from-package

.github/workflows/test-all-versions.pr.yml

@@ -27,7 +27,7 @@ jobs:
         id: lerna-args
         run: |
           OUTPUT=`node scripts/parse-lerna-scopes.mjs "$PR_LABELS"`
-          echo "::set-output name=args::$OUTPUT"
+          echo "args=$OUTPUT" >> $GITHUB_OUTPUT
 
   tav:
     uses: ./.github/workflows/test-all-versions.yml

.release-please-manifest.json

@@ -1,2 +1 @@
-{"detectors/node/opentelemetry-resource-detector-alibaba-cloud":"0.27.2","detectors/node/opentelemetry-resource-detector-aws":"1.2.0","detectors/node/opentelemetry-resource-detector-container":"0.2.0","detectors/node/opentelemetry-resource-detector-gcp":"0.27.3","detectors/node/opentelemetry-resource-detector-github":"0.27.0","detectors/node/opentelemetry-resource-detector-instana":"0.3.0","metapackages/auto-instrumentations-node":"0.34.0","metapackages/auto-instrumentations-web":"0.30.1","packages/opentelemetry-host-metrics":"0.30.1","packages/opentelemetry-id-generator-aws-xray":"1.1.1","packages/opentelemetry-propagation-utils":"0.29.0","packages/opentelemetry-test-utils":"0.32.0","plugins/node/instrumentation-amqplib":"0.31.0","plugins/node/instrumentation-dataloader":"0.2.1","plugins/node/instrumentation-fs":"0.5.1","plugins/node/instrumentation-lru-memoizer":"0.31.0","plugins/node/instrumentation-mongoose":"0.31.1","plugins/node/instrumentation-tedious":"0.4.1","plugins/node/opentelemetry-instrumentation-aws-lambda":"0.33.1","plugins/node/opentelemetry-instrumentation-aws-sdk":"0.9.3","plugins/node/opentelemetry-instrumentation-bunyan":"0.30.1","plugins/node/opentelemetry-instrumentation-cassandra":"0.31.0","plugins/node/opentelemetry-instrumentation-connect":"0.30.1","plugins/node/opentelemetry-instrumentation-dns":"0.30.1","plugins/node/opentelemetry-instrumentation-express":"0.31.3","plugins/node/opentelemetry-instrumentation-fastify":"0.30.1","plugins/node/opentelemetry-instrumentation-generic-pool":"0.30.0","plugins/node/opentelemetry-instrumentation-graphql":"0.32.0","plugins/node/opentelemetry-instrumentation-hapi":"0.30.1","plugins/node/opentelemetry-instrumentation-ioredis":"0.32.2","plugins/node/opentelemetry-instrumentation-knex":"0.30.1","plugins/node/opentelemetry-instrumentation-koa":"0.33.0","plugins/node/opentelemetry-instrumentation-memcached":"0.30.1","plugins/node/opentelemetry-instrumentation-mongodb":"0.32.2","plugins/node/opentelemetry-instrumentation-mysql":"0.31.2","plugins/node/opentelemetry-instrumentation-mysql2":"0.32.1","plugins/node/opentelemetry-instrumentation-nestjs-core":"0.31.1","plugins/node/opentelemetry-instrumentation-net":"0.30.2","plugins/node/opentelemetry-instrumentation-pg":"0.32.0","plugins/node/opentelemetry-instrumentation-pino":"0.32.1","plugins/node/opentelemetry-instrumentation-redis":"0.33.1","plugins/node/opentelemetry-instrumentation-redis-4":"0.33.1","plugins/node/opentelemetry-instrumentation-restify":"0.30.1","plugins/node/opentelemetry-instrumentation-router":"0.31.0","plugins/node/opentelemetry-instrumentation-winston":"0.30.1","plugins/web/opentelemetry-instrumentation-document-load":"0.30.1","plugins/web/opentelemetry-instrumentation-long-task":"0.31.1","plugins/web/opentelemetry-instrumentation-user-interaction":"0.31.1","plugins/web/opentelemetry-plugin-react-load":"0.28.1","propagators/opentelemetry-propagator-aws-xray":"1.1.1","propagators/opentelemetry-propagator-grpc-census-binary":"0.26.0","propagators/opentelemetry-propagator-instana":"0.2.1","propagators/opentelemetry-propagator-ot-trace":"0.26.2"}
-
+{"detectors/node/opentelemetry-resource-detector-alibaba-cloud":"0.27.5","detectors/node/opentelemetry-resource-detector-aws":"1.2.3","detectors/node/opentelemetry-resource-detector-container":"0.2.3","detectors/node/opentelemetry-resource-detector-gcp":"0.28.1","detectors/node/opentelemetry-resource-detector-github":"0.27.0","detectors/node/opentelemetry-resource-detector-instana":"0.4.2","metapackages/auto-instrumentations-node":"0.36.6","metapackages/auto-instrumentations-web":"0.32.1","packages/opentelemetry-host-metrics":"0.32.1","packages/opentelemetry-id-generator-aws-xray":"1.1.1","packages/opentelemetry-propagation-utils":"0.29.3","packages/opentelemetry-redis-common":"0.35.0","packages/opentelemetry-test-utils":"0.33.2","plugins/node/instrumentation-amqplib":"0.32.3","plugins/node/instrumentation-dataloader":"0.4.1","plugins/node/instrumentation-fs":"0.7.2","plugins/node/instrumentation-lru-memoizer":"0.32.2","plugins/node/instrumentation-mongoose":"0.32.2","plugins/node/instrumentation-socket.io":"0.33.2","plugins/node/instrumentation-tedious":"0.5.2","plugins/node/opentelemetry-instrumentation-aws-lambda":"0.35.1","plugins/node/opentelemetry-instrumentation-aws-sdk":"0.34.1","plugins/node/opentelemetry-instrumentation-bunyan":"0.31.2","plugins/node/opentelemetry-instrumentation-cassandra":"0.32.2","plugins/node/opentelemetry-instrumentation-connect":"0.31.2","plugins/node/opentelemetry-instrumentation-dns":"0.31.3","plugins/node/opentelemetry-instrumentation-express":"0.32.2","plugins/node/opentelemetry-instrumentation-fastify":"0.31.2","plugins/node/opentelemetry-instrumentation-generic-pool":"0.31.2","plugins/node/opentelemetry-instrumentation-graphql":"0.34.1","plugins/node/opentelemetry-instrumentation-hapi":"0.31.2","plugins/node/opentelemetry-instrumentation-ioredis":"0.34.1","plugins/node/opentelemetry-instrumentation-knex":"0.31.2","plugins/node/opentelemetry-instrumentation-koa":"0.34.4","plugins/node/opentelemetry-instrumentation-memcached":"0.31.2","plugins/node/opentelemetry-instrumentation-mongodb":"0.34.2","plugins/node/opentelemetry-instrumentation-mysql":"0.33.1","plugins/node/opentelemetry-instrumentation-mysql2":"0.33.2","plugins/node/opentelemetry-instrumentation-nestjs-core":"0.32.3","plugins/node/opentelemetry-instrumentation-net":"0.31.2","plugins/node/opentelemetry-instrumentation-pg":"0.35.1","plugins/node/opentelemetry-instrumentation-pino":"0.33.2","plugins/node/opentelemetry-instrumentation-redis":"0.34.5","plugins/node/opentelemetry-instrumentation-redis-4":"0.34.4","plugins/node/opentelemetry-instrumentation-restify":"0.32.2","plugins/node/opentelemetry-instrumentation-router":"0.32.2","plugins/node/opentelemetry-instrumentation-winston":"0.31.2","plugins/web/opentelemetry-instrumentation-document-load":"0.32.1","plugins/web/opentelemetry-instrumentation-long-task":"0.32.3","plugins/web/opentelemetry-instrumentation-user-interaction":"0.32.2","plugins/web/opentelemetry-plugin-react-load":"0.28.1","propagators/opentelemetry-propagator-aws-xray":"1.2.0","propagators/opentelemetry-propagator-grpc-census-binary":"0.26.0","propagators/opentelemetry-propagator-instana":"0.2.1","propagators/opentelemetry-propagator-ot-trace":"0.26.2"}

CONTRIBUTING.md

@@ -2,6 +2,27 @@
 
 We'd love your help!
 
+- [Report a bug or requesting feature](#report-a-bug-or-requesting-feature)
+- [How to contribute](#how-to-contribute)
+  - [Before you start](#before-you-start)
+    - [Conventional commit](#conventional-commit)
+  - [Fork](#fork)
+  - [Running the tests](#running-the-tests)
+  - [Generating API documentation](#generating-api-documentation)
+  - [Generating CHANGELOG documentation](#generating-changelog-documentation)
+  - [Benchmarks](#benchmarks)
+- [Component Ownership](#component-ownership)
+- [Component Lifecycle](#component-lifecycle)
+  - [Unreleased](#unreleased)
+  - [Experimental](#experimental)
+  - [Beta](#beta)
+  - [Stable](#stable)
+  - [Unmaintained](#unmaintained)
+  - [Deprecated](#deprecated)
+- [Contributing Vendor Components](#contributing-vendor-components)
+  - [Adding a New Vendor Component](#adding-a-new-vendor-component)
+  - [Removing Vendor Components](#removing-vendor-components)
+
 ## Report a bug or requesting feature
 
 Reporting bugs is an important contribution. Please make sure to include:
@@ -80,6 +101,67 @@ When two or more approaches must be compared, please write a benchmark in the be
 
 - `npm run bench` to run your benchmark.
 
+## Component Ownership
+
+This repository contains many components which are maintained by more than the typical set of JS maintainers and approvers.
+Each component in this repository SHOULD have a component owner who is responsible for maintaining it.
+The README.md for each component SHOULD contain its owner, but the source of truth for component ownership is in [.github/component_owners.yml](.github/component_owners.yml).
+Component owners are generally given authority to make decisions relating to implementation and feature requests for their components, provided they follow the best practices set out by the maintainers.
+Component owners MUST do their best to maintain a high level of quality, security, performance, and specification compliance within their components.
+Maintainers may override the decisions of component owners, but should only do so when they feel one or more of these traits is compromised.
+
+## Component Lifecycle
+
+This repository contains many components in various stages of the component lifecycle.
+A component may be **unreleased**, **experimental**, **beta**, **stable**, **unmaintained**, or **deprecated**; see the below definitions for each stability level.
+With the exception of the stable status, it is up to each individual [component owner](#component-ownership) to determine the status of a component.
+A component may only be marked stable with the approval of a member of @open-telemetry/javascript-maintainers; see the definition of stable below for more details.
+
+### Unreleased
+
+Unreleased components are in active development and have not yet been released to NPM.
+Unreleased packages should have the property `private` in their `package.json` set to `true`.
+
+### Experimental
+
+Experimental packages are in active development.
+They should be considered unstable and potentially unsuitable for production use.
+They are released to NPM for developers and early adopters.
+Experimental components MUST have their major version set to `0`.
+If a component does not have an explicit status in its README.md file, it should be considered to be experimental.
+
+### Beta
+
+Beta packages are not yet considered stable, but an effort should be made to preserve stability across versions if possible.
+They may be ready for production use, but users should understand that their APIs or the telemetry they output MAY change if required.
+Beta components MUST have their major version set to `0`.
+
+### Stable
+
+This is the highest level of quality and maintainership guarantee provided in this repository.
+Stable packages should be considered stable and ready for production use.
+In order for a package to be marked stable, it must meet the following requirements:
+
+- It MUST have a component owner that the JS maintainers feel confident will be responsive to issues and pull requests and will fulfill their responsibility competently.
+  If a component owner is not responsive to issues and PRs, the maintainers may assign a new owner or change the status of the component to unmaintained.
+- All relevant specification relating to the component MUST be stable. For example, telemetry emitted by an instrumentation library should rely on a stable semantic convention.
+- It MUST be reviewed and approved by a member of @open-telemetry/javascript-maintainers.
+
+Stable components MUST have their major version set to `1` or greater.
+
+### Unmaintained
+
+A component which does not have an assigned component owner, or has a component owner who has been unresponsive to issues and pull requests may be marked as unmaintained.
+Unmaintained components may continue to work and receive updates and fixes from contributors, but may not receive immediate attention if there is a problem or feature request.
+A component which is unmaintained may be deprecated if there is a problem that is not fixed in a timely manner.
+
+### Deprecated
+
+Deprecated components are no longer maintained and there are not currently plans to maintain them.
+They may not work and there are no guarantees for fixes or new features.
+Their source files may be deleted from the repository.
+Any packages released from their source will be marked as deprecated in NPM.
+
 ## Contributing Vendor Components
 
 This repo is generally meant for hosting components that work with popular open-source frameworks and tools. However, it is also possible to contribute components specific to a 3rd party vendor in this repo.