Skip to content

chore(deps): globals (minor → 17.5.0) #126

Open
gh-worker-campaigns-3e9aa4[bot] wants to merge 1 commit intomainfrom
engraver-auto-version-upgrade/minorpatch/npm/0-1776954908
Open

chore(deps): globals (minor → 17.5.0) #126
gh-worker-campaigns-3e9aa4[bot] wants to merge 1 commit intomainfrom
engraver-auto-version-upgrade/minorpatch/npm/0-1776954908

Conversation

@gh-worker-campaigns-3e9aa4
Copy link
Copy Markdown

Summary: Dependency update — 1 package upgraded (MINOR changes included)

Manifests changed:

  • . (yarn)

✅ Action Required: Please review the changes below. If they look good, approve and merge this PR.


Updates

Package From To Type Dep Type Vulnerabilities Fixed
globals 17.4.0 17.5.0 minor Direct -

Packages marked with "-" are updated due to dependency constraints.


Review Checklist

Standard review:

  • Review changes for compatibility with your code
  • Check for breaking changes in release notes
  • Run tests locally or wait for CI
  • Approve and merge this PR

Update Mode: Routine Update

🤖 Generated by DataDog Automated Dependency Management System

@github-actions
Copy link
Copy Markdown

Overall package size

Self size: 35.99 MB
Deduped: 35.99 MB
No deduping: 35.99 MB

Dependency sizes | name | version | self size | total size | |------|---------|-----------|------------|

🤖 This report was automatically generated by heaviest-objects-in-the-universe

@campaigner-prod campaigner-prod Bot marked this pull request as ready for review April 24, 2026 13:40
@campaigner-prod campaigner-prod Bot requested review from a team as code owners April 24, 2026 13:40
@dd-prapprover
Copy link
Copy Markdown

dd-prapprover Bot commented Apr 24, 2026

PRApprover will approve and merge this PR, FAQ, #dx-source-code-management

🛠️ PRApproval Status

  • ✅ PR is eligible for auto-approval by rule dependency-management-version-updater - 2026-04-24T13:40:54Z
  • ✅ CI tests passed - 2026-04-24T13:40:59Z
  • ✅ Approved (commit: bff6636) - 2026-04-24T13:41:01Z
  • ✅ Merge Started
  • ⬜ Merged

➡️ Current phase: merge in progress...

Copy link
Copy Markdown

@dd-prapprover dd-prapprover Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR has been automatically approved by the DD PR Approver bot.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bff66368c4

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread yarn.lock
Comment on lines +4 to +5
__metadata:
version: 8
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep lockfile in Yarn v1 format used by CI

This rewrite switches the root lockfile from Classic syntax (# yarn lockfile v1) to Berry syntax (__metadata version 8), but the repo’s workflows still run plain yarn install without pinning/enabling Yarn 4 (see .github/workflows/build.yml and .github/actions/build-test-wasm/action.yaml). In environments that resolve yarn to Yarn Classic (the previous baseline for this repo), installs will fail at lockfile parsing, so lint/build jobs break before tests even run. Please either keep the lockfile in v1 format or migrate CI to a pinned Yarn 4 toolchain in the same change.

Useful? React with 👍 / 👎.

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants