chore: release main

Author: otelbot[bot]

.editorconfig

@@ -0,0 +1,11 @@
+# http://editorconfig.org
+
+root = true
+
+[*]
+indent_style = space
+indent_size = 2
+end_of_line = lf
+charset = utf-8
+trim_trailing_whitespace = true
+insert_final_newline = true

.gitattributes

@@ -0,0 +1,40 @@
+## This .gitattributes file automatically formats the EOL character in certain filetypes within the repository
+
+## Source code
+# JavaScript, TypeScript, c, and h source files
+*.js                    text eol=lf
+*.ts                    text eol=lf
+*.tsx                   text eol=lf
+*.h                     text eol=lf diff=cpp
+*.c                     text eol=lf diff=cpp
+
+# Shell scripts
+*.sh                    text eol=lf
+*.bash                  text eol=lf
+
+# Windows batch and PowerShell scripts
+*.bat                   text eol=crlf
+*.cmd                   text eol=crlf
+*.ps1                   text eol=crlf
+
+##### Other file types #####
+
+## Text files and documentation
+*.txt                   text
+README*                 text
+RELEASING*              text
+CHANGELOG*              text
+CONTRIBUTING*           text
+INSTALL*                text
+LICENSE*                text
+
+## Non-text documentation
+*.html                  text diff=html
+*.pdf                   binary
+*.json                  text
+*.rtf                   binary
+
+## Git Properties
+.gitignore              text
+.gitmodules             text
+.gitattributes          text

.github/CODEOWNERS

@@ -0,0 +1,15 @@
+#####################################################
+#
+# List of approvers for OpenTelemetry JS SDK
+#
+#####################################################
+#
+# Learn about membership in OpenTelemetry community:
+#  https://github.com/open-telemetry/community/blob/main/community-membership.md
+#
+#
+# Learn about CODEOWNERS file format:
+#  https://help.github.com/en/articles/about-code-owners
+#
+
+*               @open-telemetry/javascript-approvers

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,34 @@
+---
+name: Bug report
+about: Create a report to help us improve
+labels: bug
+---
+
+<!-- 
+Please answer these questions before submitting a bug report.
+-->
+
+### What version of OpenTelemetry are you using?
+
+
+### What version of Node are you using?
+
+
+### What did you do?
+<!-- 
+If possible, provide a recipe for reproducing the error.
+-->
+
+
+### What did you expect to see?
+
+
+### What did you see instead?
+
+
+### Additional context
+<!-- 
+Add any other context about the problem here.
+-->
+
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>

.github/ISSUE_TEMPLATE/discussion.md

@@ -0,0 +1,15 @@
+---
+name: Discussion
+about: Ask a question or bring up points of consideration
+labels: discussion
+---
+
+<!--
+**NB:** Before opening a discussion here, please consider whether it is JS specific, or if it should be considered 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.
+-->
+
+- [ ] This only affects the JavaScript OpenTelemetry library
+- [ ] This may affect other libraries, but I would like to get opinions here first
+
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,35 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+labels: feature-request
+---
+
+<!--
+**NB:** Before opening a feature request against this repo, consider whether the feature 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.
+-->
+
+### Is your feature request related to a problem? Please describe
+<!--
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+-->
+
+
+### Describe the solution you'd like to see
+<!-- 
+A clear and concise description of what you want to happen.
+-->
+
+
+### Describe alternatives you've considered
+<!-- 
+A clear and concise description of any alternative solutions or features you've considered.
+-->
+
+
+### Additional context
+<!-- 
+Add any other context or screenshots about the feature request here.
+-->
+
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>
+

.github/ISSUE_TEMPLATE/instrumentation_request.md

@@ -0,0 +1,38 @@
+---
+name: Instrumentation request
+about: Create a request to add a new instrumentation
+labels: instrumentation-request
+---
+
+<!--
+**NB:** Before opening an instrumentation request against this repo, please read [the contributing guidelines for new instrumentation](../blob/main/CONTRIBUTING.md#new-instrumentation).
+-->
+
+### Which library do you want to instrument?
+<!--
+A clear and concise description of why this library should be instrumented. Ex. I'm always frustrated when [...]
+-->
+
+### Code Owners
+
+<!--
+New Instrumentations MUST have at least 2 code-owners that will maintain the instrumentation long-term.
+Any code-owners listed MUST fulfill all criteria laid out in the checklist below.
+-->
+
+- Owner 1
+  - [ ] I am a [member of the OpenTelemetry Organization](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#member)
+  - [ ] I have read [CONTRIBUTING.md](../blob/main/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 may be subject to the [OpenTelemetry Semantic Conventions](https://github.com/open-telemetry/semantic-conventions) and agree to follow the rules set out therein
+- Owner 2
+  <!-- instruct any co-owners to complete the checklist above and comment it on this issue -->
+  - [ ] Commented on the issue confirming they have fulfilled all criteria for becoming a component owner
+<!-- continue listing co-owners if you have more than two -->
+
+### 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?
+-->
+
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>

.github/ISSUE_TEMPLATE/ownership_request.md

@@ -0,0 +1,42 @@
+---
+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](../blob/main/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](../blob/main/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 am a [member of the OpenTelemetry Organization](https://github.com/open-telemetry/community/blob/main/guides/contributor/membership.md#member)
+- [ ] I have read [CONTRIBUTING.md](../blob/main/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
+-->
+
+<sub>**Tip**: [React](https://github.blog/news-insights/product-news/add-reactions-to-pull-requests-issues-and-comments/) with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding `+1` or `me too`, to help us triage it. Learn more [here](https://opentelemetry.io/community/end-user/issue-participation/).</sub>

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+<!--
+We appreciate your contribution to the OpenTelemetry project! 👋🎉
+
+Before creating a pull request, please make sure:
+- Your PR is solving one problem
+- Please provide enough information so that others can review your pull request
+- You have read the guide for contributing
+  - See https://github.com/open-telemetry/opentelemetry-js/blob/main/CONTRIBUTING.md
+- You signed all your commits (otherwise we won't be able to merge the PR)
+  - See https://github.com/open-telemetry/community/blob/main/guides/contributor#sign-the-cla
+- You added unit tests for the new functionality
+- You mention in the PR description which issue it is addressing, e.g. "Fixes #xxx". This will auto-close
+  the issue that your PR fixes (if such)
+-->
+
+## Which problem is this PR solving?
+
+-
+
+## Short description of the changes
+
+-