chore(deps): bump @opentelemetry/resources from 1.30.1 to 2.0.0 #283
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
Bumps [@opentelemetry/resources](https://github.com/open-telemetry/opentelemetry-js) from 1.30.1 to 2.0.0. - [Release notes](https://github.com/open-telemetry/opentelemetry-js/releases) - [Changelog](https://github.com/open-telemetry/opentelemetry-js/blob/main/CHANGELOG.md) - [Commits](open-telemetry/opentelemetry-js@v1.30.1...v2.0.0) --- updated-dependencies: - dependency-name: "@opentelemetry/resources" dependency-version: 2.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot-npm_and_yarn-opentelemetry-resources-2.0.0
branch
from
951e723 to
b5b16e6
Compare
|
/code pr |
There was a problem hiding this comment.
🤖
The changes you've shown in the package-lock.json and package.json files indicate an upgrade of the @opentelemetry/resources package from version ^1.30.1 to ^2.0.0. Here are some key points and considerations for this upgrade:
Key Changes:
-
Version Update in
package.json:- The
@opentelemetry/resourcesdependency version has been updated from^1.30.1to^2.0.0.
- The
-
Removal of Duplicated Entries in
package-lock.json:- Previously,
@opentelemetry/resourceswas listed multiple times within different subdirectories (e.g.,node_modules/@opentelemetry/sdk-trace-base/node_modules/@opentelemetry/resources). These duplicated entries have been removed as they are no longer needed since@opentelemetry/resourcesis now a top-level dependency. - The
@opentelemetry/resourcesentry at the top level has been updated to version2.0.0with:@opentelemetry/coreas a dependency version2.0.0.- The
enginesfield now specifies a more restrictive Node.js version requirement (^18.19.0 || >=20.6.0). - The
licensefield isApache-2.0. - It also depends on
@opentelemetry/semantic-conventionsat^1.29.0.
- Previously,
-
Dependencies and Compatibility:
- The
@opentelemetry/resourcespackage now requires at least Node.js version18.19.0or20.6.0and above due to the updatedenginesfield. - The semantic conventions dependency has been updated to at least
@opentelemetry/semantic-conventionsversion1.29.0. This might require you to also bump that version in your project or ensure it meets the version requirement.
- The
Steps You Should Follow:
-
Update Node.js Version:
- Make sure your project is running on Node.js version
^18.19.0or>=20.6.0. You can update your Node.js version using the package manager of your choice (e.g.,nvmfor Node Version Manager).
- Make sure your project is running on Node.js version
-
Install Updated Dependencies:
- Run
npm install(oryarn installif you are using Yarn) to install the updated versions. This command will automatically update yournode_modulesfolder andpackage-lock.jsonfile based on the version specified inpackage.json.
- Run
-
Update Other Dependencies if Necessary:
- Ensure all related dependencies are compatible with the new version of
@opentelemetry/resources. You might need to update@opentelemetry/coreand@opentelemetry/semantic-conventionsaccording to the updated dependencies listed in the@opentelemetry/resourcespackage.
- Ensure all related dependencies are compatible with the new version of
-
Review Release Notes:
- Check the release notes or changelog for
@opentelemetry/resourcesversion2.0.0for any breaking changes or new features.
- Check the release notes or changelog for
-
Run Tests:
- Run your test suite to ensure that the upgrade has not introduced any regressions.
-
Address Node.js Version Requirement:
- If your Node.js version does not meet the new requirement, you'll need to update it. Ensure your build environment and CI/CD pipelines also meet the new Node.js requirement.
-
Review Peer Dependencies:
- The peer dependency for
@opentelemetry/apinow requires at least version>=1.3.0and less than1.10.0. Ensure your project's@opentelemetry/apiversion is compatible with this requirement.
- The peer dependency for
Example Commands:
# Ensure you have the correct Node.js version
nvm install 20.6.0
nvm use 20.6.0
# Update dependencies
npm install
# Run your tests
npm testBy following these steps, you can successfully upgrade the @opentelemetry/resources package and ensure your project remains stable and compatible with the newer version.
> qwen-2.5-coder-32b [pr | 0]
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
bot
deleted the
dependabot-npm_and_yarn-opentelemetry-resources-2.0.0
branch
Bumps @opentelemetry/resources from 1.30.1 to 2.0.0.
Release notes
Sourced from
@opentelemetry/resources's releases.... (truncated)
Changelog
Sourced from
@opentelemetry/resources's changelog.... (truncated)
Commits
7fde940chore: prepare release 2.0.0/0.200.0 (#5521)ecd67dedoc: add section to SDK 2.x migration guide for implementors of resource dete...eaebf76chore: prepare release 2.0.0-rc.1/0.200.0-rc.1 (#5534)e947bd9chore(deps): update dependency babel-loader to v10 (#5518)5e20647fix(deps): update dependency axios to v1.8.2 [security] (#5532)78fc472chore(deps): lock file maintenance (#5531)693b09dfix(core): avoid using util in configuration.ts for browser compatibility (#5...92fde6achore: prepare 2.0.0-dev.1/0.200.0-dev.1 pre-release (#5512)04b3210doc: upgrade/migration guide for SDK 2.0 (#5513)cb48266fix(deps): update dependency import-in-the-middle to v1.13.1 (#5517)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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)