Archived Plugins Now Bundled into Core – Migration & Version Compatibility Questions

Product Support Self-hosting

AI-generated summary

Evie_Tao is running Discourse via the official docker setup and has been installing several plugins via Docker hooks. They noticed that these plugins were archived by the owner in July 2025 and are now read-only, as they have been bundled into Discourse core. Evie_Tao wants to confirm if they can safely delete these plugin folders and rely on the core-bundled versions. They also ask about the Discourse branch or release tag that first includes the latest bundled implementations of the plugins, any extra configuration changes or migrations needed, and any known caveats or compatibility issues. Moin confirms that all config/data will be maintained when the plugins are folded into core.

1

Hi,

I’m running Discourse via the official discourse_docker setup, and in my web_only container I currently install several plugins by cloning their repositories under /var/www/discourse/plugins using Docker hooks:

  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/discourse-oauth2-basic.git
          - git clone https://github.com/discourse/discourse-solved.git
          - git clone https://github.com/discourse/discourse-gamification.git
          - git clone https://github.com/discourse/discourse-reactions.git
          - git clone https://github.com/discourse/discourse-ai.git

I’ve noticed that each of these repositories was archived by the owner in July 2025 and now displays:
“This repository was archived by the owner on Jul xx, 2025. It is now read-only.
This plugin has now been bundled into Discourse core.”
Before I remove these clones from our Docker image, I’d like to confirm:
Can I safely delete these plugin folders under /plugins and rely purely on the core-bundled versions?

If so, which Discourse branch or release tag first includes the latest bundled implementations of:

  • oauth2-basic

  • solved

  • gamification

  • reactions

  • discourse-ai

After removing the external clones, are there any extra configuration changes or migrations needed (e.g. Site Settings, database migrations, or new feature flags)?

Any known caveats or compatibility issues when migrating from the standalone plugin versions to the core-integrated code?

I want to ensure we’re on a supported Discourse release and won’t lose any functionality when we switch over. Thanks in advance for any pointers or recommended upgrade paths!

2