Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Created by
brew bump
Created with
brew bump-formula-pr
.release notes
Other
Notice
The default Code Level Metrics configuration will change in an upcoming release from enabled to disabled.
If you do not use Code Level Metrics, you should see no impact and will not have to take any action.
If you do rely on Code Level Metrics, ensure that your newrelic.ini configuration file has the
newrelic.code_level_metrics.enabled
INI setting uncommented and set to true.e.g:
newrelic.code_level_metrics.enabled = true
This change only impacts the default configuration value. Manually set configuration values will be honored, and core CLM behavior will remain unaffected.
Support statement
New Relic recommends that you upgrade the agent regularly and at a minimum every 3 months. For more information on supported agent versions and EOL timelines, check out our New Relic PHP Agent EOL policy.
The PHP agent compatibility and requirements page should be consulted for the latest information on supported PHP versions and platforms.
For installations using an unsupported PHP version or platform, it's highly recommended that you disable the auto-update mechanisms for the PHP agent packages. This can be done by adding the PHP agent packages to an exclusion list for package upgrades. Or you could version pin the PHP agent package to an agent version that supports the old, unsupported feature(s). Failure to prevent upgrades may result in a newer agent release being installed and the removal of support for the required, unsupported features. This would disrupt APM data collection.
The PHP agent packages that are affected are: