How can I identify the sonarqube-webapp commit corresponding to a SonarQube Server release?

SonarQube Server / Community Build
,
1

Hello,

I created a Japanese localization plugin for SonarQube Community Build and SonarQube Server. Although it has not been updated since its initial release, I would now like to resume updating it for newer SonarQube versions.

Previously, I used the release tags in the sonarqube-webapp repository and generated the corresponding localization resources from the following file using a script:

libs/sq-server-commons/src/l10n/default.ts

This workflow worked for both Community Build and commercial SonarQube editions. I could check out the tag corresponding to a SonarQube release and generate the localization resources from the version of this file included in that tag.

However, while reviewing the current tags in the repository, I noticed that tags for commercial SonarQube editions no longer appear to be added. The latest one I could find was:

2025.6.0.117042

Because of this, I can no longer use the same workflow to determine which version of default.ts corresponds to a particular SonarQube Server release.

Could you please clarify the following?

  1. Is the absence of tags for commercial SonarQube editions an intentional change in the release/tagging process?
  2. Is there a recommended way to find the sonarqube-webapp commit corresponding to a specific SonarQube Server release version?

Any guidance on the recommended workflow for maintaining localization plugins for SonarQube Server would be greatly appreciated.

Thank you.

5

Hi @amoriki,

That’s good news for the Japanese community of users!

  1. I’ll be quite honest, I’m not sure why commercial version tags used to be added and stopped. I’ll ask around and see if anyone has a better memory than me.
  2. No official recommended way. You’re the first to highlight this issue!

Here’s an imperfect solution: I’d suggest using the package.json file history. It won’t be the exact commit, but there shouldn’t be too many differences on the list of key-values to translate.

In the meantime, I’ll check what changed on our side, and see if we can put automation in place to tag the commercial releases as well.

Thanks for reaching out!

6

Hi @Jeremy_Davis,

Thank you for your reply.

I understand your suggestion to use the package.json history. I will try it and see if it works for maintaining the translations.

I look forward to any further information you may find about the tagging process or automation for commercial releases.

Thanks again!