chore(deps): bump laravel/serializable-closure from 2.0.15 to 2.0.16 in the minor-and-patch group - #41797
Merged
phil-davis merged 5 commits intoAug 30, 2026
Conversation
Bumps the minor-and-patch group with 1 update: [laravel/serializable-closure](https://github.com/laravel/serializable-closure). Updates `laravel/serializable-closure` from 2.0.15 to 2.0.16 - [Release notes](https://github.com/laravel/serializable-closure/releases) - [Changelog](https://github.com/laravel/serializable-closure/blob/2.x/CHANGELOG.md) - [Commits](laravel/serializable-closure@v2.0.15...v2.0.16) --- updated-dependencies: - dependency-name: laravel/serializable-closure dependency-version: 2.0.16 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: minor-and-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
Loading composer repositories with package information Updating dependencies Lock file operations: 0 installs, 1 update, 0 removals - Upgrading sabre/event (5.1.8 => 5.1.9) Writing lock file
These two events had the same event priority. They happened to get in the right order because their event entries were sorted alphabetically, so "c" came before "h". Sabre\Event is no longer going to do this alphabetical sorting. It will trigger events in priority order, and then for events with the same priority, it will trigger the events in the order that they have been put into the listeners array. This will make the order of event execution more transparent. Signed-off-by: Phillip Davis <phil@jankaritech.com>
…ervices Updating dependencies Lock file operations: 0 installs, 13 updates, 0 removals - Upgrading google/apiclient-services (v0.452.0 => v0.456.0) - Upgrading myclabs/deep-copy (1.13.4 => 1.14.0) - Upgrading phpunit/phpunit (9.6.35 => 9.6.36) - Upgrading roave/security-advisories (dev-latest 4d2ca57 => dev-latest 6c0be3a) - Upgrading sebastian/exporter (4.0.8 => 4.0.9) - Upgrading sebastian/recursion-context (4.0.6 => 4.0.7) - Upgrading symfony/console (v7.4.16 => v7.4.17) - Upgrading symfony/event-dispatcher (v7.4.15 => v7.4.17) - Upgrading symfony/mailer (v7.4.15 => v7.4.17) - Upgrading symfony/mime (v7.4.16 => v7.4.17) - Upgrading symfony/process (v7.4.13 => v7.4.17) - Upgrading symfony/routing (v7.4.15 => v7.4.17) - Upgrading symfony/translation (v7.4.16 => v7.4.17) Writing lock file Note: the other items are dev dependencies of phpunit. They do not need tgo be in the changelog. Signed-off-by: Phillip Davis <phil@jankaritech.com>
Signed-off-by: Phillip Davis <phil@jankaritech.com>
Contributor
|
Added the other dependencies that were in PR #41676 and a changelog. |
phil-davis
approved these changes
Aug 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the minor-and-patch group with 1 update: laravel/serializable-closure.
Updates
laravel/serializable-closurefrom 2.0.15 to 2.0.16Release notes
Sourced from laravel/serializable-closure's releases.
Changelog
Sourced from laravel/serializable-closure's changelog.
Commits
7cfc24e[2.x] Ensure$signeris configured before attempting to execute `unserializ...e276c64Bump actions/checkout from 7.0.0 to 7.0.1 in the github-actions group (#173)38a5dcbUpdate CHANGELOGDependabot 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 show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions