chore(deps): bump @opentelemetry/instrumentation-pino from 0.35.0 to 0.36.0

[dependabot]

Bumps @opentelemetry/instrumentation-pino from 0.35.0 to 0.36.0.

Release notes

Sourced from @​opentelemetry/instrumentation-pino's releases.

instrumentation-user-interaction: v0.36.0

0.36.0 (2024-03-06)

Features

• deps: update otel-js to 1.22.0/0.49.1 (edc426b)

instrumentation-long-task: v0.36.0

0.36.0 (2024-03-06)

Features

• deps: update otel-js to 1.22.0/0.49.1 (edc426b)

instrumentation-document-load: v0.36.0

0.36.0 (2024-03-06)

Features

• deps: update otel-js to 1.22.0/0.49.1 (edc426b)

Commits

• f81f8a7 chore: release main (#1539)
• 8d9687d feat(fastify): Skip update HTTP's span name and update RpcMetadata's route in...
• bf25eb1 chore(renovate): change strategy for @​opentelemetry/api, run experimental upd...
• 3139dbf chore: update renovate.json (#1575)
• 273993b chore: re-enable instrumentation-fastify unit test on node@18 (#1568)
• 84a2377 fix(deps): update otel core experimental to ^0.41.0 (#1566)
• ffb45fe chore(renovate): split patch and minor rules (#1572)
• 8e2f518 feat(express): Skip update HTTP's span name and update RpcMetadata's route in...
• 774d254 fix(document-load): compatibility issue with @​opentelemetry/sdk-trace-web@​1.1...
• a18b074 docs: document merge reqiurements (#1553)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[saidsef]

/code pr

[saidsef]

🤖
No issues or suggestions for enhancements are identified within the modified lines of the provided patch. The changes are straightforward dependency updates, specifically bumping @opentelemetry/instrumentation-pino from version 0.35.0 to 0.36.0 in both package.json and package-lock.json. The modifications adhere to standard practices for updating dependencies in Node.js projects.

_{> gpt-4-turbo-preview [pr | 0]}

[saidsef]

🤖
The PR submitted by dependabot for bumping @opentelemetry/instrumentation-pino from version 0.35.0 to 0.36.0 appears to be straightforward and correctly updates both package.json and package-lock.json files. However, there are a few points to consider for enhancement and verification:

1. Dependency Verification: Ensure that the new version 0.36.0 of @opentelemetry/instrumentation-pino is fully compatible with the other @opentelemetry dependencies and the overall project. This includes checking for any breaking changes or required updates in the codebase to accommodate the new version.

2. Changelog Review: It's crucial to review the Changelog and Release notes for version 0.36.0 to understand the changes, improvements, or any deprecations that come with this update. This can help in anticipating any potential issues or adjustments needed in the project.

3. Testing: After updating the dependency, thorough testing should be conducted to ensure that the integration of @opentelemetry/instrumentation-pino version 0.36.0 does not introduce any regressions or unexpected behaviour. This includes unit tests, integration tests, and any end-to-end testing frameworks in place.

4. Peer Dependencies: The PR shows that the peer dependency @opentelemetry/instrumentation has been updated to version ^0.49.1 within the node_modules/@opentelemetry/instrumentation-pino package. Confirm that this update aligns with the project's requirements and does not conflict with other dependencies.

5. Documentation: If the project's documentation includes specific references to the version of @opentelemetry/instrumentation-pino or related setup/configuration instructions, it may need to be updated to reflect the changes introduced by the upgrade.

6. Commit Message: The commit message follows the conventional format used by dependabot. However, it might be beneficial to include a brief description of the reason for the upgrade (e.g., to leverage new features, fix specific issues, or maintain up-to-date dependencies) and any notable changes that affect the project.

In summary, the PR is well-formed, but due diligence in the form of compatibility checks, changelog review, thorough testing, and potential documentation updates is recommended before merging.

_{> gpt-4-turbo-preview [pr | 2]}

[saidsef]

@dependabot rebase

[saidsef]

LGTM