If you have a high test coverage index, and your tests for this pull request are passing, it should be both safe and recommended to merge this update.

Updated packages

Some times an update also needs new or updated dependencies to be installed. Even if this branch is for updating one dependency, it might contain other installs or updates. All of the updates in this branch can be found here:

• package/one: 2.0.1 (updated from 2.0.2)
• other/package: 2.0.0 (new package, previously not installed)
• third/removed 2.2.0 (package was removed)

Release notes

Here are the release notes for all versions released between your current running version, and the version this PR updates the package to.

Changed files

Here is a list of changed files between the version you use, and the version this pull request updates to:

  README.md
  composer.json

Changelog

Here is a list of changes between the version you use, and the version this pull request updates to:

• e8c563c47 Prepare release
• 87e59a5e7 Update
• 5b351a5de Change
• 3d938793e Fix
• fb0f0f6f8 Introduce bug
• 8f2d1c9c7 Prepare release
• 59da20d73 Update ChangeLog

Working with this branch

If you find you need to update the codebase to be able to merge this branch (for example update some tests or rebuild some assets), please note that violinist will force push to this branch to keep it up to date. This means you should not work on this branch directly, since you might lose your work. Read more about branches created by violinist.io here.

This is an automated pull request from Violinist: Continuously and automatically monitor and update your composer dependencies. Have ideas on how to improve this message? All violinist messages are open-source, and can be improved here.