Users are encountering a pink deprecation banner in Discourse after an update, related to the component-template-resolving deprecation in Ember.js. The banner is triggered by outdated theme components using deprecated <script> tags in templates, particularly in unofficial themes like Category Previews and Buttons for Scrolling. Lilly explains that these components need modernization and advises disabling them temporarily. Moin and Richie discuss how to identify the cause using the browser console, with Richie noting the issue also appears in the core Light and Dark themes, likely due to custom code. David clarifies that deprecations are warnings, not immediate breaks, and the system will continue working until September. Lilly confirms the timeline, and patrickemin thanks the community for the clarification. piffy notes that one component, Jump button, has already been updated.
Hi, after updating today to the latest release I have the dreaded 
pink banner:
With that page of explanation: Component Template Resolving | Ember.js - Deprecations
I could not understand those explanations… Could someone explain to a rather non technician? 
Thanks
Oh I realize the banner might not be pink for everyone… 
it’s because you are using 2 unofficial theme components that need to be modernized for templates and js api:
you should disable them until they are fixed. see here:
edit: keep in mind these are admin warnings - the components are not actually broken yet, but will inevitably break in a few months unless updated appropriately.
I’m getting the same warning banner after updating this morning too.
Much like @patrickemin screen shot, mine isn’t telling me the cause of the issue either 
How can I find out which component / or components are causing this banner to appear? 
Lilly shared a screenshot of the browser console. You can open it, for example, with Command+Option+J (Mac) or Control+Shift+J (Windows).
Your list seems quite long, but most of it is the same component:
or just F12 (Windows)
Did you add any custom code to it?
Ignore that, I get the same warning on Dark too.
I’m guessing that could be caused by some additional CSS or JS that I’ve added 
Sorry, overlapping posts.
Yes - lots, it must be caused by that, I’ll check it out thanks 
I’ve just posted a dedicated topic for this deprecation, and I’ll update the warning banner to link there instead of taking people directly to Ember’s docs.
To expand on this: disabling them will remove the error banner, so that’s fine if you really need to hide it.
But it’s worth noting that deprecation notices don’t mean something is broken. It means that it will be broken in future, and we’re giving developers some advanced warning of that. It’s fine to keep using these things in the meantime.
On the <script> tag deprecation, we have a timeline here - everything will keep working until September.
yea sorry about that, I should have been more clear that folks have a couple of months or so to fix these before they actually break.
Thanks everyone, that’s very clear!
The Jump button component has now been modernized 
