# 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:** 166

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [March 9, 2026, 3:40pm UTC](https://meta.discourse.org/t/bundling-more-popular-plugins-with-discourse-core/373574/166 "2026-03-09T15:40:42Z")

</div>

The cakeday plugin isn’t bundled in 3.5.4, so that’ll be why you’re not seeing it any more.

> [@mentalstring](#):
>
> However, rebuilds (of the _same Discourse version_) stopped working because cakeday had been merged into the core

Are you sure that’s why they started failing? If you saw something like:

> HINT: The plugin ‘$plugin’ is now bundled with Discourse and should not be included in your container configuration

then I’m afraid that will be shown for **any failed rebuild** when the cakeday plugin is included in the config file. This was the most efficient way we could warn people about the issue, but it can be confusing for people running older core versions.

So if you need the cakeday plugin, I think you should be able to re-add it to your app.yml file and rebuild. I suspect the failure was caused by something else, which you’ve now resolved.

As an aside: I’d strongly recommend upgrading to a supported version. 3.5 is not receiving security updates any more, and may be vulnerable to attack.

---

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