Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable30] build(deps): Bump laravel/serializable-closure from 1.3.3 to 1.3.5 #1953

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 25, 2024

Bumps laravel/serializable-closure from 1.3.3 to 1.3.5.

Release notes

Sourced from laravel/serializable-closure's releases.

v1.3.5

v1.3.4

Changelog

Sourced from laravel/serializable-closure's changelog.

v1.3.5 - 2024-09-23

v1.3.4 - 2024-08-02

Commits

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [laravel/serializable-closure](https://github.com/laravel/serializable-closure) from 1.3.3 to 1.3.5.
- [Release notes](https://github.com/laravel/serializable-closure/releases)
- [Changelog](https://github.com/laravel/serializable-closure/blob/master/CHANGELOG.md)
- [Commits](laravel/serializable-closure@v1.3.3...v1.3.5)

---
updated-dependencies:
- dependency-name: laravel/serializable-closure
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/composer/stable30/laravel/serializable-closure-1.3.5 branch from d350dcf to 1eaad5b Compare September 26, 2024 08:22
@nickvergessen
Copy link
Member

@dependabot rebase

Copy link
Contributor Author

dependabot bot commented on behalf of github Sep 26, 2024

Looks like this PR is already up-to-date with stable30! If you'd still like to recreate it from scratch, overwriting any edits, you can request @dependabot recreate.

@nickvergessen
Copy link
Member

/composer-update

Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
@nickvergessen nickvergessen changed the title build(deps): Bump laravel/serializable-closure from 1.3.3 to 1.3.5 [stable30] build(deps): Bump laravel/serializable-closure from 1.3.3 to 1.3.5 Sep 26, 2024
@nickvergessen nickvergessen merged commit cfa4111 into stable30 Sep 26, 2024
7 checks passed
@nickvergessen nickvergessen deleted the dependabot/composer/stable30/laravel/serializable-closure-1.3.5 branch September 26, 2024 13:12
@Altahrim Altahrim mentioned this pull request Oct 1, 2024
4 tasks
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.

3 participants