# Smoke-testing plugins during upgrade process

**URL:** <https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118>\
**Category:** Feature\
**Created:** [October 1, 2017, 8:18am UTC](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118 "2017-10-01T08:18:48Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![erlend\_sh](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/erlend_sh/32/119475_2.png) [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**Post date:** [October 2, 2017, 8:37am UTC](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118/14 "2017-10-02T08:37:40Z")

</div>

Some prior discussion:

[https://meta.discourse.org/t/compatibility-checks-and-stable-versioning-for-plugins/31523?u=erlend\_sh](https://meta.discourse.org/t/compatibility-checks-and-stable-versioning-for-plugins/31523)

Also noteworthy, the WordPress community developed a plugin to mitigate these types of issues:

> **[WP Rollback – Rollback Plugins and Themes](https://wordpress.org/plugins/wp-rollback/)**
>
> Rollback (or forward) any WordPress.org plugin, theme, or block like a boss.

* * *

In short, I’m in favour of adding headers for `Requires at least` and `Tested up to`, which will prompt a warning if the Discourse version doesn’t match.

---

_[View the full topic](https://meta.discourse.org/t/smoke-testing-plugins-during-upgrade-process/71118)._