mirror of
https://github.com/certbot/certbot.git
synced 2026-01-26 07:41:33 +03:00
ac2d691ade
Coming out of the conversation at #7863 in the linked Google Doc, we should always have at least 1 release between updating one of our plugins to stop using a deprecated acme/certbot API and removing it from acme/certbot. Doing this gives the plugin changes time to propagate rather than potentially having the plugin break because Certbot was updated before the plugin had made the necessary changes. This comment here should help ensure this. * Add pytest warnings warning. * clarify comment
17 lines
880 B
INI
17 lines
880 B
INI
# This file isn't used while testing packages in tools/_release.sh so any
|
|
# settings we want to also change there must be added to the release script
|
|
# directly.
|
|
[pytest]
|
|
# In general, all warnings are treated as errors. Here are the exceptions:
|
|
# 1- decodestring: https://github.com/rthalley/dnspython/issues/338
|
|
# Warnings being triggered by our plugins using deprecated features in
|
|
# acme/certbot should be fixed by having our plugins no longer using the
|
|
# deprecated code rather than adding them to the list of ignored warnings here.
|
|
# Fixing things in this way prevents us from shipping packages raising our own
|
|
# deprecation warnings and gives time for plugins that don't use the deprecated
|
|
# API to propagate, especially for plugins packaged as an external snap, before
|
|
# we release breaking changes.
|
|
filterwarnings =
|
|
error
|
|
ignore:decodestring:DeprecationWarning
|