Skip to content

chore(deps): bump the production-dependencies group across 1 directory with 6 updates - #4907

Merged
ildyria merged 2 commits into
masterfrom
dependabot/composer/production-dependencies-0b7cd889d9
Oct 20, 2026
Merged

ildyria merged 2 commits into
masterfrom
dependabot/composer/production-dependencies-0b7cd889d9

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the production-dependencies group with 6 updates in the / directory:

Package From To
dedoc/scramble 0.13.47 0.13.48
farzai/color-palette 2.0.0 3.0.0
laravel/framework 13.35.0 13.37.0
laravel/octane 2.21.0 2.22.0
mavinoo/laravel-batch 2.5.1 3.3.0
symfony/cache 8.1.8 8.1.9

Updates dedoc/scramble from 0.13.47 to 0.13.48

Release notes

Sourced from dedoc/scramble's releases.

v0.13.48

What's Changed

🚨 Breaking changes 🚨

TL;DR: toArray method on OpenAPI objects is no longer called when serialising OpenAPI document. If you didn't extend/change toArray, you will not be affected.

This release introduces OpenAPI 3.2 support (opt-in, 3.1 is the default, results in 3.1.2 in document, and 3.2 results in 3.2.1 version in the document), hence some changes to OpenAPI objects serialisation must've been made. toArray on these objects (in Generator namespace) is kept for backward compatibility, but is not longer called when serialising the document. Instead, serializeAs31 is called.

Added

Changes

New Contributors

Full Changelog: dedoc/scramble@v0.13.47...v0.13.48

Commits

Updates farzai/color-palette from 2.0.0 to 3.0.0

Release notes

Sourced from farzai/color-palette's releases.

3.0.0

A major release that makes color extraction stable and correct. Each extraction now keeps the best of up to ten seeded, count-weighted k-means++ runs instead of relying on a single random start, so re-encoded or resized copies of an image usually come back with nearly the same palette. Both drivers now weight pixels by opacity, GD reads palette images (GIF, PNG-8) correctly, and the Imagick driver converts CMYK and wide-gamut RGB images through their embedded ICC profile. The public extraction API is unchanged, but palettes differ from 2.x, a few extension points for subclasses have changed, and ImagickImage no longer frees an \Imagick you pass it.

Breaking Changes

  • Extracted palettes differ from 2.x for most images. Extraction is still deterministic, but the colors are not the ones 2.x returned. If you cache, store or snapshot extracted palettes, re-baseline them after upgrading. The new clustering changes the palette of most images; the fixes below change some kinds of image much more: GD palette images (GIF, PNG-8, 8-bit grayscale PNG), images with transparent or semi-transparent pixels on either driver, and on Imagick, CMYK images, ICC-tagged RGB images and images in any other colorspace that is neither sRGB nor gray (for example Lab or linear RGB), which are now converted to sRGB instead of having their raw channels read as RGB. On Imagick, an image tagged with an sRGB profile other than the ICC's own, as many sRGB images are, now takes the same shrink-and-convert path; the extra shrink step moved its palette up to 3 dE00 (median 0.7) from an untagged copy.

  • On Imagick, palettes of profile-tagged images depend on the ImageMagick build. The same image always yields the same palette on the same PHP and ImageMagick build. Whether a CMYK or ICC-tagged RGB image goes through its profile or falls back depends on ImageMagick having the lcms delegate, so if your hosts or containers differ, re-baseline cached palettes per environment.

  • initializeCentroids() has a new signature. It now receives the random source to draw from:

    // 2.x
    protected function initializeCentroids(array $colors, int $k): array
    // 3.0
    protected function initializeCentroids(array $colors, int $k, \Random\Randomizer $randomizer): array

    A subclass of AbstractColorExtractor, GdColorExtractor or ImagickColorExtractor that overrides it with the old signature fails with a fatal error when the class is loaded. A subclass that calls it with the old two arguments, for example from an overridden clusterColors(), does not fail loudly: extract() catches the ArgumentCountError and returns the grayscale fallback palette, and with the default NullLogger nothing is reported. Pass a PSR-3 logger to the extractor while you test the upgrade.

    The method is called once per restart, up to ten times per extraction, with one shared generator: an override must draw from $randomizer rather than seed its own generator, or every restart starts from the same centroids. It now receives a 0-based list whose colors hold only r, g, b (rounded to integers) and count, and the centroids it returns must have integer channels; float centroids cause a TypeError that extract() also turns into the fallback palette. A library that has to support both majors can declare the third parameter as ?\Random\Randomizer $randomizer = null and draw from it when it is given.

  • calculateColorDistance() no longer decides cluster assignment. Centroid seeding and cluster assignment now use squared Euclidean RGB distance directly. Overriding calculateColorDistance() raises no error, but it now only affects the convergence check, so a custom distance metric silently stops shaping the palette.

  • The protected $seed no longer gives alternative palettes. It still seeds the generator, but best-of-ten clustering is designed not to depend on the draw, so changing it now has little effect on the result.

  • Color counts seen by subclasses are opacity-weighted. The protected extractColors() of GdColorExtractor and ImagickColorExtractor now returns each color's count in 1/127ths: an opaque pixel counts 127, a half-transparent one about half that, and fully transparent pixels are left out. A subclass that reads count, for example in an overridden processColors(), gets an opacity-weighted count of sampled pixels by dividing by 127 (equal to the sampled-pixel count for opaque images). Clustering uses counts only as relative weights, so the bundled extractors are unaffected.

  • ImagickImage no longer clears the \Imagick it wraps, and ImagickImage::__destruct() is removed. The wrapper now borrows the object it is given, as GdImage does (see Fixes). Images loaded through ImageFactory::fromPath() / createFromPath(), ImageLoader, ColorPalette::fromImage() or ColorPaletteBuilder are still freed when the image is released, because the wrapper is the only holder. If you construct new ImagickImage($imagick) yourself, keep your own reference, and relied on the wrapper going away to free its pixel memory, call $imagick->clear() when you are done with it. A subclass whose destructor calls parent::__destruct() must drop that call; otherwise it throws an Error when the wrapper is destroyed.

Packaging and licensing

  • The package now ships a file under a licence other than MIT. resources/icc/sRGB2014.icc is the ICC's sRGB profile, unaltered; the Imagick driver uses it to convert CMYK and wide-gamut RGB images to sRGB. It is distributed under the ICC's terms, which permit redistribution without restriction, not under the package's MIT licence; see resources/icc/README.md. composer.json still declares MIT, which covers the package's own code.
  • Keep resources/ when you deploy or prune vendor/. The Imagick driver reads this file for every image that embeds a CMYK or RGB ICC profile, which includes most camera and phone photos. Without it, extraction of those images emits a PHP warning and returns the grayscale fallback palette; the error itself is reported only through a PSR-3 logger you pass to the extractor.
  • Profile conversion needs ImageMagick built with lcms. Without it, CMYK images fall back to the formula conversion, and RGB images are read as sRGB, as they were in 2.x.

Fixes

  • Stable palettes (#53). Extraction was already repeatable, but the palette depended on a single random draw: across seeds 0-199 the photo from #13 produced 53 (GD) and 64 (Imagick) different palettes, and a re-encoded or upscaled copy could come back with different colors. Extraction now runs up to ten restarts of count-weighted k-means++ (the first centroid chosen by pixel count, each further one by pixel count times squared distance) from one locally seeded generator, and keeps the run with the lowest weighted squared error. Over seeds 0-19 and the shipped seed 42, the #13 photo and ten re-encoded and resized copies of it kept their palettes within a CIEDE2000 (dE00) difference of 2.3 of the original's with both drivers (very small thumbnails on the GD driver drift a little further); on a deliberately ambiguous synthetic image one case still flips. PHP's global RNG is still left untouched, and the draws use 31 bits, so 32-bit and 64-bit PHP builds give the same palette.
  • GD palette images (#53). For GIF, PNG-8 and 8-bit grayscale PNG images, imagecolorat() returns a palette index rather than an RGB value, and 2.x read that index as the blue channel. These images came back as shades of pure blue, near-black for small palettes, or the grayscale fallback. The index is now resolved through the image's palette; pixels that reference an index the palette does not define (a malformed file) are skipped.
  • CMYK and other non-sRGB images on Imagick (#53, #55). Pixel channels were read as R/G/B whatever the image's colorspace, so CMYK images came back in the wrong colors. Images in a colorspace other than sRGB or gray are now converted to sRGB. When a CMYK image embeds a CMYK ICC profile, as Photoshop CMYK exports do, the conversion goes through that profile: the plain CMYK formula missed by up to 23 dE00 on test photos, while the profile path kept 8 photos x 2 profiles within 1.45 dE00 of a full-size conversion. A profile that is corrupt, is not a CMYK profile, or cannot be applied because ImageMagick was built without lcms falls back to the formula.
  • Wide-gamut RGB images on Imagick (#58). ImageMagick reports every RGB image as sRGB whatever profile it embeds, so Adobe RGB (1998), Display P3 and ProPhoto RGB images came back duller than they are. Across 18 photos, the color furthest off in each palette was a median 3 (Display P3) to 5 (Adobe RGB) dE00 from the sRGB original's, and over 10 for 3 of them. An RGB image whose profile is not byte-identical to the shipped sRGB2014.icc is now converted through that profile, which kept every Adobe RGB and Display P3 palette within 1.6 dE00 of the original; re-encoding the original as JPEG moves it up to 1.7. Without a usable profile, or on an ImageMagick built without lcms, pixels are read as sRGB as before. The GD driver does no color management and reads every image as sRGB.
  • Transparent images (#56, #57). Neither driver weighted pixels by their alpha. GD ignored it, so a fully transparent pixel counted as whatever color was stored under it: a PNG with an invisible green under its transparent background got 2 of 5 swatches in that green. Imagick's alpha-weighted resize to its 50x50 sample already turned fully transparent pixels black (and dropped them as too dark), but every other pixel counted as opaque: a nearly invisible background kept its color and could take swatches, and an entirely transparent image came back as [#000000](https://github.com/parsilver/color-palette-php/issues/000000) swatches. Both drivers now skip fully transparent pixels and count a partially transparent pixel in proportion to its opacity, measured on GD's scale of 0 to 127, so they agree on which pixels are invisible. On GD this covers truecolor images and palette transparency (a GIF's transparent index, PNG-8 transparency). An entirely transparent image now returns the grayscale fallback palette on both drivers. Opaque images are not affected by this change: 133 GD and 225 Imagick palettes of opaque images were byte-identical with and without it.
  • ImagickImage no longer empties the caller's \Imagick (#54). Its destructor called clear() on an object it only borrowed. A caller that wrapped one \Imagick twice had it emptied when the first wrapper went away, so the next extract() silently returned the grayscale fallback palette, and any later use of the caller's object failed too.

Performance

  • Extraction does more clustering work. Ten restarts make clustering cost grow about tenfold; the assignment loop is now inlined with squared integer distances to win part of that back. Measured when the clustering change landed in #53, on a 1600x2292 photo extracting 5 colors (PHP 8.4, Linux), the GD driver went from about 0.09 s to about 0.4 s and the Imagick driver from about 0.05 s to about 0.1 s; higher color counts cost proportionally more. Extracting a single color, or an image with no more distinct colors than requested, stops after the first run.
  • Color conversion on Imagick runs on a reduced image. Images that are converted to sRGB (CMYK, ICC-tagged RGB other than the ICC's own sRGB profile, and other non-sRGB colorspaces) are shrunk to at most 200x200 first. On a 48 MP CMYK JPEG, extraction now peaks at 415 MB and takes 1.8 s, against 412 MB and 1.3 s just to decode the file; converting at full size would have peaked at 678 MB and taken 24 s. On a 48 MP Display P3 JPEG the conversion had no measurable cost (0.25 s, 325 MB either way). sRGB images without a profile or with the ICC's own sRGB profile, and grayscale images, skip this step.

Internal / Tooling

  • Extraction tests that can fail (#53). The idempotence tests added for #13 extracted from a single-color image, on which every k-means start gives the same answer, so they also passed against the unfixed code. They are replaced by a deterministic synthetic photo on which k-means is sensitive to its starting point, with tests for a GD golden palette, independence from the extractor instance and from PHP's global RNG, equality across processes, and brightest-first ordering. The basic extraction tests now pin their driver and assert that they do not get the fallback palette.
  • ICC test fixtures built in memory (#55, #58). A CMYK profile with dot gain that the formula misreads by up to 64 per channel, and a wide-gamut RGB profile (ROMM primaries, 1.8 gamma), so the profile paths are only satisfied by a real profile conversion.
  • Memory release test (#54). A test checks through ImageMagick's resource counters that images created by ImageFactory release their pixel cache, where the ImageMagick build reports it.
  • actions/checkout bumped from 6 to 7 (#52).

... (truncated)

Changelog

Sourced from farzai/color-palette's changelog.

3.0.0 - 2026-10-11

A major release that makes color extraction stable and correct. Each extraction now keeps the best of up to ten seeded, count-weighted k-means++ runs instead of relying on a single random start, so re-encoded or resized copies of an image usually come back with nearly the same palette. Both drivers now weight pixels by opacity, GD reads palette images (GIF, PNG-8) correctly, and the Imagick driver converts CMYK and wide-gamut RGB images through their embedded ICC profile. The public extraction API is unchanged, but palettes differ from 2.x, a few extension points for subclasses have changed, and ImagickImage no longer frees an \Imagick you pass it.

Breaking Changes

  • Extracted palettes differ from 2.x for most images. Extraction is still deterministic, but the colors are not the ones 2.x returned. If you cache, store or snapshot extracted palettes, re-baseline them after upgrading. The new clustering changes the palette of most images; the fixes below change some kinds of image much more: GD palette images (GIF, PNG-8, 8-bit grayscale PNG), images with transparent or semi-transparent pixels on either driver, and on Imagick, CMYK images, ICC-tagged RGB images and images in any other colorspace that is neither sRGB nor gray (for example Lab or linear RGB), which are now converted to sRGB instead of having their raw channels read as RGB. On Imagick, an image tagged with an sRGB profile other than the ICC's own, as many sRGB images are, now takes the same shrink-and-convert path; the extra shrink step moved its palette up to 3 dE00 (median 0.7) from an untagged copy.

  • On Imagick, palettes of profile-tagged images depend on the ImageMagick build. The same image always yields the same palette on the same PHP and ImageMagick build. Whether a CMYK or ICC-tagged RGB image goes through its profile or falls back depends on ImageMagick having the lcms delegate, so if your hosts or containers differ, re-baseline cached palettes per environment.

  • initializeCentroids() has a new signature. It now receives the random source to draw from:

    // 2.x
    protected function initializeCentroids(array $colors, int $k): array
    // 3.0
    protected function initializeCentroids(array $colors, int $k, \Random\Randomizer $randomizer): array

    A subclass of AbstractColorExtractor, GdColorExtractor or ImagickColorExtractor that overrides it with the old signature fails with a fatal error when the class is loaded. A subclass that calls it with the old two arguments, for example from an overridden clusterColors(), does not fail loudly: extract() catches the ArgumentCountError and returns the grayscale fallback palette, and with the default NullLogger nothing is reported. Pass a PSR-3 logger to the extractor while you test the upgrade.

    The method is called once per restart, up to ten times per extraction, with one shared generator: an override must draw from $randomizer rather than seed its own generator, or every restart starts from the same centroids. It now receives a 0-based list whose colors hold only r, g, b (rounded to integers) and count, and the centroids it returns must have integer channels; float centroids cause a TypeError that extract() also turns into the fallback palette. A library that has to support both majors can declare the third parameter as ?\Random\Randomizer $randomizer = null and draw from it when it is given.

  • calculateColorDistance() no longer decides cluster assignment. Centroid seeding and cluster assignment now use squared Euclidean RGB distance directly. Overriding calculateColorDistance() raises no error, but it now only affects the convergence check, so a custom distance metric silently stops shaping the palette.

  • The protected $seed no longer gives alternative palettes. It still seeds the generator, but best-of-ten clustering is designed not to depend on the draw, so changing it now has little effect on the result.

  • Color counts seen by subclasses are opacity-weighted. The protected extractColors() of GdColorExtractor and ImagickColorExtractor now returns each color's count in 1/127ths: an opaque pixel counts 127, a half-transparent one about half that, and fully transparent pixels are left out. A subclass that reads count, for example in an overridden processColors(), gets an opacity-weighted count of sampled pixels by dividing by 127 (equal to the sampled-pixel count for opaque images). Clustering uses counts only as relative weights, so the bundled extractors are unaffected.

  • ImagickImage no longer clears the \Imagick it wraps, and ImagickImage::__destruct() is removed. The wrapper now borrows the object it is given, as GdImage does (see Fixes). Images loaded through ImageFactory::fromPath() / createFromPath(), ImageLoader, ColorPalette::fromImage() or ColorPaletteBuilder are still freed when the image is released, because the wrapper is the only holder. If you construct new ImagickImage($imagick) yourself, keep your own reference, and relied on the wrapper going away to free its pixel memory, call $imagick->clear() when you are done with it. A subclass whose destructor calls parent::__destruct() must drop that call; otherwise it throws an Error when the wrapper is destroyed.

Packaging and licensing

  • The package now ships a file under a licence other than MIT. resources/icc/sRGB2014.icc is the ICC's sRGB profile, unaltered; the Imagick driver uses it to convert CMYK and wide-gamut RGB images to sRGB. It is distributed under the ICC's terms, which permit redistribution without restriction, not under the package's MIT licence; see resources/icc/README.md. composer.json still declares MIT, which covers the package's own code.
  • Keep resources/ when you deploy or prune vendor/. The Imagick driver reads this file for every image that embeds a CMYK or RGB ICC profile, which includes most camera and phone photos. Without it, extraction of those images emits a PHP warning and returns the grayscale fallback palette; the error itself is reported only through a PSR-3 logger you pass to the extractor.
  • Profile conversion needs ImageMagick built with lcms. Without it, CMYK images fall back to the formula conversion, and RGB images are read as sRGB, as they were in 2.x.

Fixes

  • Stable palettes (#53). Extraction was already repeatable, but the palette depended on a single random draw: across seeds 0-199 the photo from #13 produced 53 (GD) and 64 (Imagick) different palettes, and a re-encoded or upscaled copy could come back with different colors. Extraction now runs up to ten restarts of count-weighted k-means++ (the first centroid chosen by pixel count, each further one by pixel count times squared distance) from one locally seeded generator, and keeps the run with the lowest weighted squared error. Over seeds 0-19 and the shipped seed 42, the #13 photo and ten re-encoded and resized copies of it kept their palettes within a CIEDE2000 (dE00) difference of 2.3 of the original's with both drivers (very small thumbnails on the GD driver drift a little further); on a deliberately ambiguous synthetic image one case still flips. PHP's global RNG is still left untouched, and the draws use 31 bits, so 32-bit and 64-bit PHP builds give the same palette.
  • GD palette images (#53). For GIF, PNG-8 and 8-bit grayscale PNG images, imagecolorat() returns a palette index rather than an RGB value, and 2.x read that index as the blue channel. These images came back as shades of pure blue, near-black for small palettes, or the grayscale fallback. The index is now resolved through the image's palette; pixels that reference an index the palette does not define (a malformed file) are skipped.
  • CMYK and other non-sRGB images on Imagick (#53, #55). Pixel channels were read as R/G/B whatever the image's colorspace, so CMYK images came back in the wrong colors. Images in a colorspace other than sRGB or gray are now converted to sRGB. When a CMYK image embeds a CMYK ICC profile, as Photoshop CMYK exports do, the conversion goes through that profile: the plain CMYK formula missed by up to 23 dE00 on test photos, while the profile path kept 8 photos x 2 profiles within 1.45 dE00 of a full-size conversion. A profile that is corrupt, is not a CMYK profile, or cannot be applied because ImageMagick was built without lcms falls back to the formula.
  • Wide-gamut RGB images on Imagick (#58). ImageMagick reports every RGB image as sRGB whatever profile it embeds, so Adobe RGB (1998), Display P3 and ProPhoto RGB images came back duller than they are. Across 18 photos, the color furthest off in each palette was a median 3 (Display P3) to 5 (Adobe RGB) dE00 from the sRGB original's, and over 10 for 3 of them. An RGB image whose profile is not byte-identical to the shipped sRGB2014.icc is now converted through that profile, which kept every Adobe RGB and Display P3 palette within 1.6 dE00 of the original; re-encoding the original as JPEG moves it up to 1.7. Without a usable profile, or on an ImageMagick built without lcms, pixels are read as sRGB as before. The GD driver does no color management and reads every image as sRGB.
  • Transparent images (#56, #57). Neither driver weighted pixels by their alpha. GD ignored it, so a fully transparent pixel counted as whatever color was stored under it: a PNG with an invisible green under its transparent background got 2 of 5 swatches in that green. Imagick's alpha-weighted resize to its 50x50 sample already turned fully transparent pixels black (and dropped them as too dark), but every other pixel counted as opaque: a nearly invisible background kept its color and could take swatches, and an entirely transparent image came back as [#000000](https://github.com/parsilver/color-palette-php/issues/000000) swatches. Both drivers now skip fully transparent pixels and count a partially transparent pixel in proportion to its opacity, measured on GD's scale of 0 to 127, so they agree on which pixels are invisible. On GD this covers truecolor images and palette transparency (a GIF's transparent index, PNG-8 transparency). An entirely transparent image now returns the grayscale fallback palette on both drivers. Opaque images are not affected by this change: 133 GD and 225 Imagick palettes of opaque images were byte-identical with and without it.
  • ImagickImage no longer empties the caller's \Imagick (#54). Its destructor called clear() on an object it only borrowed. A caller that wrapped one \Imagick twice had it emptied when the first wrapper went away, so the next extract() silently returned the grayscale fallback palette, and any later use of the caller's object failed too.

Performance

  • Extraction does more clustering work. Ten restarts make clustering cost grow about tenfold; the assignment loop is now inlined with squared integer distances to win part of that back. Measured when the clustering change landed in #53, on a 1600x2292 photo extracting 5 colors (PHP 8.4, Linux), the GD driver went from about 0.09 s to about 0.4 s and the Imagick driver from about 0.05 s to about 0.1 s; higher color counts cost proportionally more. Extracting a single color, or an image with no more distinct colors than requested, stops after the first run.

... (truncated)

Commits
  • a5a777d fix(extractor): convert wide-gamut RGB images through their ICC profile (#58)
  • 8dc57ca Merge remote-tracking branch 'origin/main' into claude/elated-fermi-6e399e
  • f170c26 Merge pull request #59 from parsilver/docs/dedupe-transparency-note
  • a41cfa8 docs: drop the stale GD-only transparency note from UPGRADING.md
  • 428c13a Merge pull request #57 from parsilver/claude/determined-fermat-fb4b95
  • 1f3b417 Merge remote-tracking branch 'origin/main' into claude/elated-fermi-6e399e
  • 5fb8600 Merge pull request #56 from parsilver/claude/intelligent-goldstine-0433cf
  • 2c0a9c5 Merge remote-tracking branch 'origin/main' into claude/elated-fermi-6e399e
  • d84a6f1 fix(extractor): convert CMYK images through their embedded ICC profile (#55)
  • e8f62b8 refactor(extractor): read the sRGB profile in one expression
  • Additional commits viewable in compare view

Updates laravel/framework from 13.35.0 to 13.37.0

Release notes

Sourced from laravel/framework's releases.

v13.37.0

v13.36.0

... (truncated)

Changelog

Sourced from laravel/framework's changelog.

v13.37.0 - 2026-10-16

v13.36.0 - 2026-10-13

... (truncated)

Commits
  • 685f8d6 Update version to v13.37.0
  • af81bbb [13.x] Improve exception reporting (#62047)
  • fbc2b3e Release the unique lock when pushing a queued listener fails (#62045)
  • 6d2eefb [13.x] Suppress teardown warnings when disconnecting dead connections (#62042)
  • ff0d6b9 [13.x] Don't report skipped migrations as pending in migrate:status (#61989)
  • bff5d2a [13.x] Fix cached Attribute accessors returning stale values after setting ...
  • 940f345 add Stringable to the parameter types in Rule::when() and Rule::unless() (#62...
  • c413cff [13.x] Fix DynamoDbStore::many() returning values under the wrong keys for ...
  • 9bfc373 Add strict option to Rule::numeric() (#62031)
  • da949b4 [13.x] Fix encrypted:object and encrypted:collection casts always being d...
  • Additional commits viewable in compare view

Updates laravel/octane from 2.21.0 to 2.22.0

Release notes

Sourced from laravel/octane's releases.

v2.22.0

Changelog

Sourced from laravel/octane's changelog.

v2.22.0 - 2026-10-14

Commits
  • c49ff45 [2.x] Su...

    Description has been truncated

@dependabot
dependabot Bot requested a review from a team as a code owner October 19, 2026 20:54
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file php Pull requests that update Php code labels Oct 19, 2026
@coderabbitai

coderabbitai Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Organization UI
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: f2e61266-8166-4381-abe2-0ed0fdbd7397

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@socket-security

socket-security Bot commented Oct 19, 2026 •

Copy link
Copy Markdown

…y with 6 updates

Bumps the production-dependencies group with 6 updates in the / directory:

| Package | From | To |
| --- | --- | --- |
| [dedoc/scramble](https://github.com/dedoc/scramble) | `0.13.47` | `0.13.48` |
| [farzai/color-palette](https://github.com/parsilver/color-palette-php) | `2.0.0` | `3.0.0` |
| [laravel/framework](https://github.com/laravel/framework) | `13.35.0` | `13.37.0` |
| [laravel/octane](https://github.com/laravel/octane) | `2.21.0` | `2.22.0` |
| [mavinoo/laravel-batch](https://github.com/mavinoo/laravelBatch) | `2.5.1` | `3.3.0` |
| [symfony/cache](https://github.com/symfony/cache) | `8.1.8` | `8.1.9` |



Updates `dedoc/scramble` from 0.13.47 to 0.13.48
- [Release notes](https://github.com/dedoc/scramble/releases)
- [Commits](dedoc/scramble@v0.13.47...v0.13.48)

Updates `farzai/color-palette` from 2.0.0 to 3.0.0
- [Release notes](https://github.com/parsilver/color-palette-php/releases)
- [Changelog](https://github.com/parsilver/color-palette-php/blob/main/CHANGELOG.md)
- [Commits](parsilver/color-palette-php@2.0.0...3.0.0)

Updates `laravel/framework` from 13.35.0 to 13.37.0
- [Release notes](https://github.com/laravel/framework/releases)
- [Changelog](https://github.com/laravel/framework/blob/13.x/CHANGELOG.md)
- [Commits](laravel/framework@v13.35.0...v13.37.0)

Updates `laravel/octane` from 2.21.0 to 2.22.0
- [Release notes](https://github.com/laravel/octane/releases)
- [Changelog](https://github.com/laravel/octane/blob/2.x/CHANGELOG.md)
- [Commits](laravel/octane@v2.21.0...v2.22.0)

Updates `mavinoo/laravel-batch` from 2.5.1 to 3.3.0
- [Release notes](https://github.com/mavinoo/laravelBatch/releases)
- [Changelog](https://github.com/mavinoo/laravelBatch/blob/master/CHANGELOG.md)
- [Upgrade guide](https://github.com/mavinoo/laravelBatch/blob/master/UPGRADE.md)
- [Commits](mavinoo/laravelBatch@v2.5.1...v3.3.0)

Updates `symfony/cache` from 8.1.8 to 8.1.9
- [Release notes](https://github.com/symfony/cache/releases)
- [Changelog](https://github.com/symfony/cache/blob/8.2/CHANGELOG.md)
- [Commits](symfony/cache@v8.1.8...v8.1.9)

---
updated-dependencies:
- dependency-name: dedoc/scramble
  dependency-version: 0.13.48
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
- dependency-name: farzai/color-palette
  dependency-version: 3.0.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production-dependencies
- dependency-name: laravel/framework
  dependency-version: 13.37.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: laravel/octane
  dependency-version: 2.22.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: production-dependencies
- dependency-name: mavinoo/laravel-batch
  dependency-version: 3.3.0
  dependency-type: direct:production
  update-type: version-update:semver-major
  dependency-group: production-dependencies
- dependency-name: symfony/cache
  dependency-version: 8.1.9
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: production-dependencies
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/composer/production-dependencies-0b7cd889d9 branch from eb95e67 to 75d0f69 Compare October 20, 2026 00:03
@codecov

codecov Bot commented Oct 20, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.31%. Comparing base (a7894ea) to head (27bb039).
⚠️ Report is 1 commits behind head on master.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ildyria
ildyria merged commit 344b2c9 into master Oct 20, 2026
56 checks passed
@ildyria
ildyria deleted the dependabot/composer/production-dependencies-0b7cd889d9 branch October 20, 2026 12:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file php Pull requests that update Php code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant