# Bundling more popular plugins with Discourse core

**URL:** https://meta.discourse.org/t/bundling-more-popular-plugins-with-discourse-core/373574
**Category:** Announcements
**Created:** [July 10, 2025, 10:15am UTC](https://meta.discourse.org/t/bundling-more-popular-plugins-with-discourse-core/373574 "2025-07-10T10:15:25Z")
**Posts on this page:** 1
**Showing post:** 40

<div class="post-metadata">

### Author: ![j.jaffeux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/j.jaffeux/32/60297_2.png) [@j.jaffeux](https://meta.discourse.org/u/j.jaffeux)
#### Post date: [July 23, 2025, 8:38am UTC](https://meta.discourse.org/t/bundling-more-popular-plugins-with-discourse-core/373574/40 "2025-07-23T08:38:17Z")

</div>

> [@hellekin](#):
>
> Can the [@team](https://meta.discourse.org/groups/team) clarify the rationale behind this change?

It’s already been answered in the op:

> [@david](#):
>
> it’ll be easier for us to keep them all tested & up-to-date.

Few examples of this:

- we don’t have to worry about versioning if we add something in core for a plugin, we know that both of them are at the same version
- easier to test a plugin depending on another plugin if the code is present for both
- when we change something in core we often have to do multiple PRs just to fix specs in plugins, now it means only one standalone PR

End result is more available time for the Discourse team to improve and maintain the product instead of dealing with this kind of issues, so eventually, you win too.

---

_[View the full topic](https://meta.discourse.org/t/bundling-more-popular-plugins-with-discourse-core/373574)._