Sometimes deprecations are logged while our agent is running on a customer's machine. Some of those deprecations would be raised in the course of running our tests, but we suppress log output for our tests to avoid noisy output.
For our core technologies, can we devise a way to periodically review deprecation warnings to proactively resolve issues before new gem releases?
Sometimes deprecations are logged while our agent is running on a customer's machine. Some of those deprecations would be raised in the course of running our tests, but we suppress log output for our tests to avoid noisy output.
For our core technologies, can we devise a way to periodically review deprecation warnings to proactively resolve issues before new gem releases?