Bump composer/xdebug-handler to 1.3.0

[phil-davis]

Description

composer update composer/xdebug-handler

from 1.2.1 to 1.3.0

Motivation and Context

The bot does not seem to have found the composer/xdebug-handler 1.3.0 version bump that is waiting.

How Has This Been Tested?

CI

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

Open tasks:

• Backport (if applicable set "backport-request" label and remove when the backport was done)

[codecov]

Codecov Report

Merging #32976 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master   #32976   +/-   ##
=========================================
  Coverage     64.14%   64.14%           
  Complexity    18724    18724           
=========================================
  Files          1185     1185           
  Lines         70460    70460           
  Branches       1270     1270           
=========================================
  Hits          45198    45198           
  Misses        24892    24892           
  Partials        370      370

Flag	Coverage Δ	Complexity Δ
#javascript	52.89% <ø> (ø)	0 <ø> (ø)	⬇️
#phpunit	65.42% <ø> (ø)	18724 <ø> (ø)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 16e204e...848b3df. Read the comment docs.

[PVince81]

I don't see xdebug-handler in composer.json so assuming this is a dependency pulled indirectly through other libs, which explains why only composer.lock needed an update.

[PVince81]

👍

[phil-davis]

I don't see xdebug-handler in composer.json so assuming this is a dependency pulled indirectly through other libs, which explains why only composer.lock needed an update.

Yes, I was doing a "default" composer update and noticed that it wanted to suck this in.