Alexander Grimalovsky

I've updated Travis CI configuration to use the [minimal currently supported](https://ubuntu.com/about/release-cycle#server-desktop-eol) version of Ubuntu and [currently supported](https://nodejs.org/en/about/releases/) versions of Node.js. The setup of Chrome is updated to the [currently supported](https://docs.travis-ci.com/user/chrome#selecting-a-chrome-version)...

@ericelliott It looks like it is required to make a change in the repository configuration from your side. Travis CI is migrated from `travis-ci.org` to the `travis-ci.com` ([docs](https://docs.travis-ci.com/user/migrate/open-source-on-travis-ci-com/), blog posts:...

@kampeador It looks like we're very close to getting this merged, could you please consider addressing the latest review comments? Thank you in advance. I hope it will be enough...

@jarednova @gchtr is there is any plans to raise minimum supported version for Timber 2.x to 7.1 or 7.2? Even 7.1 had reached its end of life [over a month...

@jarednova Of course you know it better, but since it is new major version - it opens a possibility to uplift environment requirements. From same statistics it can be seen...

At my sight there should be at least a way to control resizing process. For example [\Timber\Image\Operation\Resize::get_target_sizes()](https://github.com/timber/timber/blob/master/lib/Image/Operation/Resize.php#L85) may have Wordpress filters to decide if image should be upscaled. Something like:...

I've filled in separate issue #1799 before finding this one, it is directly related. I will close it in favor of this one but want to mention it due to...

@Tulipesz The reason of the issue is the use of `cuid` library in Bugsnag. I've already sent PR https://github.com/ericelliott/cuid/pull/264 to the original library, but it is not merged yet. Bugsnag...

May it be worth going in the same way (https://github.com/symfony/symfony/pull/36655) as Symfony does for its Doctrine transport for Messenger and automatically add `doctrine_migration_versions` into schema?

Unfortunately, it looks like filtering of the `doctrine_migration_versions` breaks the migration process itself because the same schema filter is applied for the [migration process itself](https://github.com/doctrine/migrations/blob/f24167d7a41ed8062338c87a5a1e776caef3e514/lib/Doctrine/Migrations/Tools/Console/Command/MigrateCommand.php#L144).