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

Lock file maintenance #206

Merged
merged 1 commit into from
Mar 2, 2024
Merged

Lock file maintenance #206

merged 1 commit into from
Mar 2, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 2, 2023

Mend Renovate

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 4am on Monday" in timezone UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

Read more information about the use of Renovate Bot within Laminas.

@renovate renovate bot added the renovate label Oct 2, 2023
@renovate
Copy link
Contributor Author

renovate bot commented Oct 2, 2023

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.


  • Branch has one or more failed status checks

@Ocramius
Copy link
Member

Ocramius commented Oct 3, 2023

Did we just break @psalm spectacularly?

PHP Fatal error:  Allowed memory size of 8589934592 bytes exhausted (tried to allocate 20480 bytes) in /github/workspace/vendor/vimeo/psalm/src/Psalm/Internal/Type/TypeExpander.php on line 287

@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from e2d5601 to 4e6c575 Compare October 11, 2023 18:26
@boesing
Copy link
Member

boesing commented Oct 11, 2023

@Ocramius actually, I broke psalm and fixed it in 5.x-dev, sadly there is no 5.16 yet which will resolve this problem...
I am fine with merging this for now, I am thinking of pinning psalm to a commit until 5.16 is out.
Maybe I do this in this PR for now, I do follow releases of psalm via github and will remove the commit pinning once a release is available.

@renovate

This comment was marked as outdated.

@boesing boesing force-pushed the renovate/lock-file-maintenance branch 2 times, most recently from e296e2d to 4e6c575 Compare October 11, 2023 22:26
@renovate renovate bot changed the base branch from 4.0.x to 3.23.x October 24, 2023 11:22
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 4e6c575 to 46e05e9 Compare October 24, 2023 11:22
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot changed the base branch from 3.23.x to 4.0.x March 2, 2024 22:40
@renovate renovate bot force-pushed the renovate/lock-file-maintenance branch from 46e05e9 to c7edb25 Compare March 2, 2024 22:40
@boesing boesing merged commit d69bfef into 4.0.x Mar 2, 2024
37 of 40 checks passed
@boesing boesing deleted the renovate/lock-file-maintenance branch March 2, 2024 23:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants