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

fix(deps): update dependency fruitcake/laravel-cors to v2 - autoclosed #34

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 16, 2020

WhiteSource Renovate

This PR contains the following updates:

Package Type Update Change
fruitcake/laravel-cors require major 1.0.3 -> 2.0.4

Release Notes

fruitcake/laravel-cors

v2.0.4

Compare Source

To avoid memory leaks with Octane (https://github.com/fruitcake/laravel-cors/pull/469)

v2.0.3

Compare Source

v2.0.2

Compare Source

Add support for Laravel 8, drop unsupported versions.

v2.0.1

Compare Source

Uses v2.0.1 of stack-cors, re-enables reflective headers instead of wildcards.

v2.0.0

Compare Source

v2.0 (2020-05-11)

asm89/stack-cors 2.x is now used, with these notable changes:

Added
Changed

v1.0.6

Compare Source

v1.0.5

Compare Source

Validate config values when creating the Service, instead of when used.

v1.0.4

Compare Source


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate
Copy link
Author

renovate bot commented May 16, 2020

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻️ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you check the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: composer.lock
Command failed: docker run --rm --name=renovate_composer --label=renovate_child -v "/mnt/renovate/gh/alouini333/DocDoc_api":"/mnt/renovate/gh/alouini333/DocDoc_api" -v "/tmp/renovate-cache":"/tmp/renovate-cache" -e COMPOSER_CACHE_DIR -e COMPOSER_AUTH -w "/mnt/renovate/gh/alouini333/DocDoc_api" docker.io/renovate/composer:1.10.21 bash -l -c "composer update fruitcake/laravel-cors --with-dependencies --ignore-platform-reqs --no-ansi --no-interaction --no-scripts --no-autoloader"
Dependency "laravel/framework" is also a root requirement, but is not explicitly allowed. Ignoring.
Loading composer repositories with package information
Updating dependencies (including require-dev)
PHP Fatal error:  Allowed memory size of 1610612736 bytes exhausted (tried to allocate 4096 bytes) in phar:///usr/local/composer/1.10.21/bin/composer/src/Composer/DependencyResolver/Solver.php on line 223

@renovate renovate bot force-pushed the renovate/fruitcake-laravel-cors-2.x branch from 01bdfb7 to 7c2f0ac Compare July 1, 2020 20:17
@renovate renovate bot force-pushed the renovate/fruitcake-laravel-cors-2.x branch from 7c2f0ac to 241b292 Compare April 26, 2021 16:52
@renovate renovate bot changed the title chore(deps): update dependency fruitcake/laravel-cors to v2 fix(deps): update dependency fruitcake/laravel-cors to v2 Apr 26, 2021
@renovate renovate bot changed the title fix(deps): update dependency fruitcake/laravel-cors to v2 fix(deps): update dependency fruitcake/laravel-cors to v2 - autoclosed Mar 7, 2022
@renovate renovate bot closed this Mar 7, 2022
@renovate renovate bot deleted the renovate/fruitcake-laravel-cors-2.x branch March 7, 2022 11:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant