# Package rules changelog strange behaviour

**URL:** <https://community.sonarsource.com/t/package-rules-changelog-strange-behaviour/190353>\
**Category:** SonarQube Server / Community Build\
**Tags:** rule-changes, sonarqube\
**Created:** [October 21, 2026, 9:20am UTC](https://community.sonarsource.com/t/package-rules-changelog-strange-behaviour/190353 "2026-10-21T09:20:34Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Usinelogicielle](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/usinelogicielle/32/64329_2.png) [@Usinelogicielle](https://community.sonarsource.com/u/Usinelogicielle)\
**Post date:** [October 21, 2026, 9:20am UTC](https://community.sonarsource.com/t/package-rules-changelog-strange-behaviour/190353/1 "2026-10-21T09:20:34Z")

</div>

Hello!  
Since our last version upgrade of SonarQube to 26.7.0.124771-community, we’ve seen a strange behaviour in the rules changelog of a package (see screenshot below).  
Basically, there’s multiple blocks of Updated and Activated changes for the same date and time. Is there a reason for all the Activated changes not to be grouped together in the same block?

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/f/e/fe8071f2c9f2ed4658e4a9ab21d87990193180c8.png)

---

<div class="post-metadata">

**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\
**Post date:** [October 23, 2026, 1:34pm UTC](https://community.sonarsource.com/t/package-rules-changelog-strange-behaviour/190353/2 "2026-10-23T13:34:22Z")

</div>

Hi @Usinelogicielle, from which version did you update? If we know both your origin and target version, we could reproduce it and be able to tell you more about it.

---

<div class="post-metadata">

**Author:** ![Usinelogicielle](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/usinelogicielle/32/64329_2.png) [@Usinelogicielle](https://community.sonarsource.com/u/Usinelogicielle)\
**Post date:** [October 23, 2026, 2:17pm UTC](https://community.sonarsource.com/t/package-rules-changelog-strange-behaviour/190353/3 "2026-10-23T14:17:49Z")

</div>

Hi @andres and thank you for your answer, we were on version 25.6.0.109173-community before the update.

---

<div class="post-metadata">

**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\
**Post date:** [October 23, 2026, 3:08pm UTC](https://community.sonarsource.com/t/package-rules-changelog-strange-behaviour/190353/4 "2026-10-23T15:08:45Z")

</div>

Did you update directly from 25.6 to 26.7 or did you make an intermediate stop in 25.12? As per our [update path calculator](https://docs.sonarsource.com/sonarqube-community-build/server-update-and-maintenance/update/determine-path), 25.12 is a mandatory milestone.

 ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/a/a/aa9912e03ba450e5186d1939ffaf23c2cc8a647b.png)

---

<div class="post-metadata">

**Author:** ![Usinelogicielle](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/usinelogicielle/32/64329_2.png) [@Usinelogicielle](https://community.sonarsource.com/u/Usinelogicielle)\
**Post date:** [October 26, 2026, 8:12am UTC](https://community.sonarsource.com/t/package-rules-changelog-strange-behaviour/190353/5 "2026-10-26T08:12:03Z")

</div>

Hi @andres, we made an intermediate stop at 25.12 and a second at 26.1.

---

<div class="post-metadata">

**Author:** ![andres](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/andres/32/76342_2.png) [@andres](https://community.sonarsource.com/u/andres)\
**Post date:** [October 26, 2026, 2:12pm UTC](https://community.sonarsource.com/t/package-rules-changelog-strange-behaviour/190353/6 "2026-10-26T14:12:53Z")

</div>

Thanks for confirming. I’m going to flag this for the team, perhaps they can share some insight about how does this work.

---

<div class="post-metadata">

**Author:** ![kim.phan](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/kim.phan/32/76093_2.png) [@kim.phan](https://community.sonarsource.com/u/kim.phan)\
**Post date:** [October 29, 2026, 11:10am UTC](https://community.sonarsource.com/t/package-rules-changelog-strange-behaviour/190353/11 "2026-10-29T11:10:19Z")

</div>

Hello @Usinelogicielle , the changelog lists rows in time order, from newest to oldest (considering the seconds). To keep it readable, the date is shown only once per minute, and the action type (activated, updated, etc.) is shown only once for consecutive actions of the same type. So the rows are not grouped by action types.

In your case, some activations happened, then updates, then deactivations, and then more activations, thus those two blocks of activations.

I hope it answers!
