Merge branch 'main' into esbuild-plugin

Author: drewcorlin1

.github/ISSUE_TEMPLATE/plugin_request.md renamed to .github/ISSUE_TEMPLATE/instrumentation_request.md

@@ -5,9 +5,7 @@ labels: instrumentation-request
 ---
 
 <!--
-**NB:** Before opening an instrumentation request against this repo, consider whether the instrumentation should/could be implemented in the [other OpenTelemetry client libraries](https://github.com/open-telemetry/). If so, please [open an issue on opentelemetry-specification](https://github.com/open-telemetry/opentelemetry-specification/issues/new) first.
-
-You are welcome to try to build your own instrumentation. If you do, please let us know if you have any questions/feedback.
+**NB:** Before opening an instrumentation request against this repo, please read [the contributing guidelines for new instrumentation](../../CONTRIBUTING.md#new-instrumentation).
 -->
 
 ### Is your instrumentation request related to a problem? Please describe
@@ -27,6 +25,15 @@ Weekly Downloads:
 
 Versions:
 
+### Code Owners
+
+<!--
+New Instrumentation requests need at least 2 code-owners that will maintain the instrumentation long-term.
+-->
+
+- Owner 1
+- Owner 2
+
 ### Additional context
 <!--
 Add any other context or screenshots about the instrumentation request here. Is there a reference you could point for the well-defined lifecycle methods?

.github/ISSUE_TEMPLATE/ownership_request.md

@@ -0,0 +1,39 @@
+---
+name: Component Ownership Request
+about: Request yourself being added as a component owner for a component in this repository
+labels: type:ownership-request
+---
+
+<!--
+**NB:** Before opening a component ownership request against this repo, please read [CONTRIBUTING.md](../../CONTRIBUTING.md#component-ownership) and its subsections first.
+-->
+
+### Which component are you requesting ownership of?
+
+<!--
+Put a link to the component here.
+-->
+
+### Related Work and Qualifications
+
+<!--
+List here why you're qualified to take ownership of the component, see [CONTRIBUTING.md](../../CONTRIBUTING.md#becoming-a-component-owner) for details.
+
+Examples:
+- I am working on <related open-source-project> and have deep knowledge of the instrumented package.
+- I am using the instrumented package on a regular basis and have deep knowledge of the instrumented package.
+- I am working on <similar package or system> and have deep knowledge of the concepts of the instrumented package.
+- I am an engineer at an observability vendor we would like to sponsor this component.
+-->
+
+### Checklist
+
+- [ ] I have read [CONTRIBUTING.md](../../CONTRIBUTING.md) and understand the responsibilities of a component owner.
+- [ ] I agree to follow and uphold the [mission, vision and values](https://github.com/open-telemetry/community/blob/main/mission-vision-values.md) of the OpenTelemetry project
+- [ ] I understand that the component I'm requesting ownership of may be subject to the [OpenTelemetry Semantic Conventions](https://github.com/open-telemetry/semantic-conventions) and agree to follow the rules set out therein.
+
+### Additional context
+
+<!--
+Add any other context that does not fit any of the above sections
+-->

.github/component-label-map.yml

@@ -32,6 +32,10 @@ pkg:resource-detector-instana:
       - any-glob-to-any-file:
           - detectors/node/opentelemetry-resource-detector-instana/**
           - packages/opentelemetry-test-utils/**
+pkg:auto-configuration-propagators:
+  - changed-files:
+      - any-glob-to-any-file:
+          - metapackages/auto-configuration-propagators/**
 pkg:auto-instrumentations-node:
   - changed-files:
       - any-glob-to-any-file:
@@ -270,3 +274,35 @@ pkg:sql-common:
   - changed-files:
       - any-glob-to-any-file:
           - packages/opentelemetry-sql-common/**
+pkg:propagator-aws-xray:
+  - changed-files:
+      - any-glob-to-any-file:
+          - propagators/propagator-aws-xray/**
+pkg:propagator-aws-xray-lambda:
+  - changed-files:
+      - any-glob-to-any-file:
+          - propagators/propagator-aws-xray-lambda/**
+pkg-status:unmaintained:
+  - changed-files:
+      - any-glob-to-any-file:
+          - detectors/node/opentelemetry-resource-detector-github/**
+          - packages/opentelemetry-redis-common/**
+          - plugins/node/instrumentation-fs/**
+          - plugins/node/instrumentation-tedious/**
+          - plugins/node/opentelemetry-instrumentation-connect/**
+          - plugins/node/opentelemetry-instrumentation-dns/**
+          - plugins/node/opentelemetry-instrumentation-fastify/**
+          - plugins/node/opentelemetry-instrumentation-generic-pool/**
+          - plugins/node/opentelemetry-instrumentation-hapi/**
+          - plugins/node/opentelemetry-instrumentation-knex/**
+          - plugins/node/opentelemetry-instrumentation-koa/**
+          - plugins/node/opentelemetry-instrumentation-memcached/**
+          - plugins/node/opentelemetry-instrumentation-mongodb/**
+          - plugins/node/opentelemetry-instrumentation-mysql/**
+          - plugins/node/opentelemetry-instrumentation-mysql2/**
+          - plugins/node/opentelemetry-instrumentation-nestjs-core/**
+          - plugins/node/opentelemetry-instrumentation-restify/**
+          - plugins/node/opentelemetry-instrumentation-router/**
+          - propagators/opentelemetry-propagator-ot-trace/**
+          - propagators/propagator-aws-xray/**
+          - propagators/propagator-aws-xray-lambda/**

.github/component_owners.yml

@@ -3,7 +3,7 @@ components:
   detectors/node/opentelemetry-resource-detector-alibaba-cloud:
     - legendecas
   detectors/node/opentelemetry-resource-detector-aws:
-    - carolabadeer
+    - jj22ee
   detectors/node/opentelemetry-resource-detector-azure:
     - jacksonweber
     - hectorhdzg
@@ -13,12 +13,13 @@ components:
     - aabmass
     - punya
   detectors/node/opentelemetry-resource-detector-github: []
-    # Unmaintained?
+    # Unmaintained
   detectors/node/opentelemetry-resource-detector-instana:
-    - basti1302
     - kirrg001
   incubator/opentelemetry-sampler-aws-xray:
-    - carolabadeer
+    - jj22ee
+  metapackages/auto-configuration-propagators:
+    - pichlermarc
   metapackages/auto-instrumentations-node:
     - dyladan
     - pichlermarc
@@ -37,14 +38,14 @@ components:
   packages/opentelemetry-host-metrics:
     - legendecas
   packages/opentelemetry-id-generator-aws-xray:
-    - carolabadeer
+    - jj22ee
   packages/opentelemetry-propagation-utils:
     - dyladan
     - pichlermarc
     - legendecas
     - blumamir
-  packages/opentelemetry-redis-common:
-    - haddasbronfman
+  packages/opentelemetry-redis-common: []
+    # Unmaintained
   packages/opentelemetry-test-utils:
     - dyladan
     - pichlermarc
@@ -58,8 +59,8 @@ components:
     - Ugzuzg
   plugins/node/instrumentation-dataloader:
     - henrinormak
-  plugins/node/instrumentation-fs:
-    - rauno56
+  plugins/node/instrumentation-fs: []
+    # Unmaintained
   plugins/node/instrumentation-kafkajs:
     - seemk
   plugins/node/instrumentation-lru-memoizer:
@@ -68,68 +69,66 @@ components:
     - blumamir
   plugins/node/instrumentation-socket.io:
     - mottibec
-    - rauno56
-  plugins/node/instrumentation-tedious:
-    - rauno56
+  plugins/node/instrumentation-tedious: []
+    # Unmaintained
   plugins/node/opentelemetry-instrumentation-aws-lambda:
-    - carolabadeer
+    - jj22ee
   plugins/node/opentelemetry-instrumentation-aws-sdk:
-    - carolabadeer
     - blumamir
+    - jj22ee
   plugins/node/opentelemetry-instrumentation-bunyan:
     - seemk
     - trentm
   plugins/node/opentelemetry-instrumentation-cassandra:
     - seemk
   plugins/node/opentelemetry-instrumentation-connect: []
-    # Unmaintained?
+    # Unmaintained
   plugins/node/opentelemetry-instrumentation-dns: []
-    # Unmaintained?
+    # Unmaintained
   plugins/node/opentelemetry-instrumentation-express:
     - JamieDanielson
     - pkanal
-  plugins/node/opentelemetry-instrumentation-fastify:
-    - pichlermarc
-  plugins/node/opentelemetry-instrumentation-generic-pool:
-    - rauno56
+  plugins/node/opentelemetry-instrumentation-fastify: []
+    # Unmaintained
+  plugins/node/opentelemetry-instrumentation-generic-pool: []
+    # Unmaintained
   plugins/node/opentelemetry-instrumentation-graphql:
     - obecny
   plugins/node/opentelemetry-instrumentation-hapi: []
-    # Unmaintained?
+    # Unmaintained
   plugins/node/opentelemetry-instrumentation-ioredis:
     - blumamir
     - naseemkullah
-  plugins/node/opentelemetry-instrumentation-knex:
-    - rauno56
+  plugins/node/opentelemetry-instrumentation-knex: []
+    # Unmaintained
   plugins/node/opentelemetry-instrumentation-koa: []
-    # Unmaintained?
-  plugins/node/opentelemetry-instrumentation-memcached:
-    - rauno56
-  plugins/node/opentelemetry-instrumentation-mongodb:
-    - osherv
-  plugins/node/opentelemetry-instrumentation-mysql:
-    - haddasbronfman
-  plugins/node/opentelemetry-instrumentation-mysql2:
-    - haddasbronfman
-  plugins/node/opentelemetry-instrumentation-nestjs-core:
-    - rauno56
+    # Unmaintained
+  plugins/node/opentelemetry-instrumentation-memcached: []
+    # Unmaintained
+  plugins/node/opentelemetry-instrumentation-mongodb: []
+    # Unmaintained
+  plugins/node/opentelemetry-instrumentation-mysql: []
+    # Unmaintained
+  plugins/node/opentelemetry-instrumentation-mysql2: []
+    # Unmaintained
+  plugins/node/opentelemetry-instrumentation-nestjs-core: []
+    # Unmaintained
   plugins/node/opentelemetry-instrumentation-net:
     - seemk
   plugins/node/instrumentation-runtime-node:
     - d4nyll
   plugins/node/opentelemetry-instrumentation-pg:
     - maryliag
-    - rauno56
   plugins/node/opentelemetry-instrumentation-pino:
     - seemk
   plugins/node/opentelemetry-instrumentation-redis-4:
     - blumamir
   plugins/node/opentelemetry-instrumentation-redis:
     - blumamir
-  plugins/node/opentelemetry-instrumentation-restify:
-    - rauno56
-  plugins/node/opentelemetry-instrumentation-router:
-    - rauno56
+  plugins/node/opentelemetry-instrumentation-restify: []
+    # Unmaintained
+  plugins/node/opentelemetry-instrumentation-router: []
+    # Unmaintained
   plugins/node/instrumentation-undici:
     - david-luna
     - trentm
@@ -146,10 +145,13 @@ components:
   plugins/web/opentelemetry-plugin-react-load:
     - martinkuba
   propagators/opentelemetry-propagator-instana:
-    - basti1302
     - kirrg001
   propagators/opentelemetry-propagator-ot-trace: []
-    # Unmaintained?
+    # Unmaintained
+  propagators/propagator-aws-xray:
+    - jj22ee
+  propagators/propagator-aws-xray-lambda: [ ]
+  # Unmaintained
 
 ignored-authors:
   - renovate-bot

.github/workflows/close-stale.yml

@@ -1,7 +1,7 @@
 name: 'Close stale issues and PRs'
 on:
   schedule:
-    - cron: '30 6 * * 1'
+    - cron: '30 6 * * *'
 
 jobs:
   stale:
@@ -20,3 +20,27 @@ jobs:
           exempt-issue-labels: never-stale
           exempt-pr-labels: never-stale
           any-of-labels: information-requested
+      - uses: actions/stale@v9
+        with:
+          days-before-issue-stale: 0
+          days-before-issue-close: 14
+          stale-issue-message: 'This package does not have an assigned [component owner](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#component-ownership) and is considered [unmaintained](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#unmaintained). As such this package is in feature-freeze and this issue will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
+
+          Are you familiar with this package? Consider [becoming a component owner](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#becoming-a-component-owner).'
+          close-issue-message: 'This issue was closed because no owner or sponsor has been found after 14 days'
+          stale-issue-label: pkg-status:unmaintained:autoclose-scheduled
+          only-labels: pkg-status:unmaintained,feature-request
+          exempt-issue-labels: bug,has:sponsor,type:semconv-update
+          remove-stale-when-updated: false
+      - uses: actions/stale@v9
+        with:
+          days-before-pr-stale: 0
+          days-before-pr-close: 14
+          stale-pr-message: 'This package does not have an assigned [component owner](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#component-ownership) and is considered [unmaintained](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#unmaintained). As such this package is in feature-freeze and this PR will be closed with 14 days unless a new owner or a sponsor (a member of @open-telemetry/javascript-approvers) for the feature is found. It is the responsibility of the author to find a sponsor for this feature.
+
+          Are you familiar with this package? Consider [becoming a component owner](https://github.com/open-telemetry/opentelemetry-js-contrib/blob/main/CONTRIBUTING.md#becoming-a-component-owner).'
+          close-pr-message: 'This issue was closed because no owner or sponsor has been found after 14 days'
+          stale-pr-label: pkg-status:unmaintained:autoclose-scheduled
+          only-labels: pkg-status:unmaintained
+          exempt-pr-labels: 'bug,has:sponsor,type:semconv-update,dependencies,autorelease: pending'
+          remove-stale-when-updated: false

.github/workflows/codeql-analysis.yml

@@ -2,17 +2,9 @@ name: "CodeQL Analysis"
 
 on:
   workflow_dispatch:
-  schedule:
-    #        ┌───────────── minute (0 - 59)
-    #        │  ┌───────────── hour (0 - 23)
-    #        │  │ ┌───────────── day of the month (1 - 31)
-    #        │  │ │ ┌───────────── month (1 - 12 or JAN-DEC)
-    #        │  │ │ │ ┌───────────── day of the week (0 - 6 or SUN-SAT)
-    #        │  │ │ │ │
-    #        │  │ │ │ │
-    #        │  │ │ │ │
-    #        *  * * * *
-    - cron: '30 1 * * *'
+  push:
+    branches: [ main ]
+  pull_request:
 
 jobs:
   CodeQL-Build:

.github/workflows/lint.yml

@@ -19,4 +19,3 @@ jobs:
       - name: Lint
         run: |
           npm run lint
-          npm run lint:markdown

.github/workflows/peer-api.yaml

@@ -10,7 +10,7 @@ jobs:
   peer-api-check:
     runs-on: ubuntu-latest
     container:
-      image: node:18
+      image: node:20
     steps:
       - name: Checkout
         uses: actions/checkout@v4

.github/workflows/release-please-validate.yaml

@@ -10,7 +10,7 @@ jobs:
   rp-validate:
     runs-on: ubuntu-latest
     container:
-      image: node:14
+      image: node:20
     steps:
       - name: Checkout
         uses: actions/checkout@v4

.github/workflows/release-please.yml

@@ -7,13 +7,18 @@ name: Run Release Please
 jobs:
   release-please:
     runs-on: ubuntu-latest
+    permissions:
+      id-token: write
     steps:
       # The logic below handles the npm publication:
       - name: Checkout Repository
         uses: actions/checkout@v4
         with:
           fetch-depth: 0
 
+      # If you update this version make sure to keep in sync:
+      # - `build-and-cache` job of unit-test workflow
+      # - `build-and-cache` job of test-all-versions workflow
       - name: Setup Node
         uses: actions/setup-node@v4
         with:
@@ -24,7 +29,7 @@ jobs:
         run: |
           npm ci
 
-      - uses: googleapis/release-please-action@f3969c04a4ec81d7a9aa4010d84ae6a7602f86a7 # v4.1.1
+      - uses: googleapis/release-please-action@7987652d64b4581673a76e33ad5e98e3dd56832f # v4.1.3
         id: release
         with:
           token: ${{secrets.RELEASE_PR_TOKEN}}
@@ -75,4 +80,5 @@ jobs:
         if: ${{ steps.release.outputs.releases_created }}
         env:
           NODE_AUTH_TOKEN: ${{secrets.NPM_TOKEN}}
+          NPM_CONFIG_PROVENANCE: true
         run: npx lerna publish from-package --no-push --no-private --no-git-tag-version --no-verify-access --yes