Skip to content

[Snyk] Upgrade @opentelemetry/resources from 2.11.0 to 2.12.0 - #255

Closed
cld-sec wants to merge 1 commit into
masterfrom
snyk-upgrade-711381d04c3b4a6703d23e9ff50b2b17
Closed

cld-sec wants to merge 1 commit into
masterfrom
snyk-upgrade-711381d04c3b4a6703d23e9ff50b2b17

Conversation

@cld-sec

@cld-sec cld-sec commented Oct 29, 2026

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to upgrade @opentelemetry/resources from 2.11.0 to 2.12.0.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.

  • The recommended version was released 22 days ago.

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Snyk has created this PR to upgrade @opentelemetry/resources from 2.11.0 to 2.12.0.

See this package in yarn:
@opentelemetry/resources

See this project in Snyk:
https://app.snyk.io/org/cloudinaryltd/project/49b18dd8-4139-4a46-8963-719d2e981418?utm_source=github&utm_medium=referral&page=upgrade-pr
@cld-sec

cld-sec commented Oct 29, 2026

Copy link
Copy Markdown
Contributor Author

Merge Risk: Medium

This upgrade to version 2.12.0 introduces significant changes to the package structure and build outputs, which may affect build tooling and certain import patterns.

Key Changes:

  • Build Output Directory: Emitted files have moved from build/src, build/esm, and build/esnext to a unified dist/ directory.
  • File Extensions: The build now uses .cjs and .mjs file extensions for CommonJS and ESM modules, respectively.
  • Build Tooling Impact: These changes could require updates to bundlers, resolvers, or build scripts that have hardcoded paths to the old build output directories.
  • package.json Import: Direct importing of <package>/package.json is no longer supported.

Recommendation:
Review your build and deployment configurations to ensure they are compatible with the new dist/ directory structure and module file extensions. Verify that you are not relying on importing package.json directly.

Source: Release notes

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants