# Discourse AI **URL:** https://meta.discourse.org/t/discourse-ai/259214 **Category:** Plugin **Tags:** official, included-in-core, ai **Created:** [24 april 2023 om 19:39 UTC](https://meta.discourse.org/t/discourse-ai/259214 "2023-04-24T19:39:41Z") **Posts on this page:** 1 **Showing post:** 215
### Author: ![rkttu](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rkttu/32/511584_2.png) [@rkttu](https://meta.discourse.org/u/rkttu) #### Post date: [10 juli 2025 om 07:54 UTC](https://meta.discourse.org/t/discourse-ai/259214/215 "2025-07-10T07:54:15Z")
After installing the Discourse AI plugin on the stable version of Discourse (3.4.6), I realized that Discourse says that [#bdef136](https://github.com/discourse/discourse-ai/commit/bdef136080074a993e7c4f5ca562edc31a8ba756) (commit dated February 4, 2025) is the latest commit, and that the currently installed plugin is the latest. However, when I checked again because there was a problem where the key fields required for AWS Bedrock integration were not displayed, I found that it was at least 300 commits behind, and when I actually went to the discourse-ai repository and checked the main branch, the gap was large. This symptom also appears in other Discourse instances that I manage, and I can’t figure out what the problem is. It hasn’t even been a week since I installed the discourse-ai plugin on my existing instance, but the commit of the version that was actually installed is more than 4-5 months old, and I’m curious about why it’s showing as the latest, and how to fix it so that the plugin can be replaced with the latest commit. --- _[View the full topic](https://meta.discourse.org/t/discourse-ai/259214)._