As per my comments in #1162:

• Deprecated features should be a warning
• Removed features should be an error
• New features should be an error
• For the few things which don't fall in the above categories: whether it is an error/warning should depend on how PHP handles the issue, i.e. does it cause a PHP parse/fatal error or a notice or warning to be thrown ?

Similarly for the error

Description of the feature

It would be nice to be able to forward some environment variables from the untrusted host e.g. by specifying their names in the manifest.
Example use case: providing the application with a ip+port/domain to connect to (which by definition can be manipulated by the untrusted host anyway).

Please note that this is a different feature than `loader.insecure__use_ho

I am contributing to a project where the maintainer has set up revapi. Sometimes when I e.g. add a new method to a public API, revapi warns me during the maven build, that this will break semantic versioning. And I think this is great.

But then I got a problem, because I don't know by heart, if I have to increase the patch, minor or even the major version. So it would be really helpful to inclu

CompatHelper can open many PRs and push all non-CompatHelper related PRs off the first page of a project's PR list. It would be great if CompatHelper labeled its auto-generated PRs with a CompatHelper label so it is easy to filter out these PRs with a simple -label:compathelper argument to the PR search.

cc: @leios @vchuravy