# 9.9.6 LTA release notes **URL:** \ **Category:** SonarQube Server / Community Build\ **Created:** [August 2, 2024, 6:48am UTC](https://community.sonarsource.com/t/9-9-6-lta-release-notes/120083 "2024-08-02T06:48:58Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![popac00](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@popac00](https://community.sonarsource.com/u/popac00)\ **Post date:** [August 2, 2024, 6:48am UTC](https://community.sonarsource.com/t/9-9-6-lta-release-notes/120083/1 "2024-08-02T06:48:58Z")
Make sure to tell us: - What version are you upgrading from? Upgrading from 9.9 LTA - System information (Operating system, Java version, Database provider/version) Postgresql 14.12 I’m now in the process of upgrading to 9.9.6 LTS, what does it mean by this release notes “In your GitHub integration configuration, when you update the GitHub URL, you must now clear the secret beforehand, and provide it again after the URL update.” Current version of my sonarqube is 9.9 LTA and it’s working seamlessly with Github Enterprise. I just got this release notes from [[SONAR-22366] Security fix (SSF-571) - Jira (atlassian.net)](https://sonarsource.atlassian.net/issues/?jql=project%20%3D%2010139%20AND%20fixVersion%20%3D%2015633%20AND%20issuetype%20!%3D%20Task) ---
**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\ **Post date:** [August 5, 2024, 5:52am UTC](https://community.sonarsource.com/t/9-9-6-lta-release-notes/120083/2 "2024-08-05T05:52:19Z")
It just means you cannot reuse the secret by changing the GitHub URL (let’s say, for example, the URL of your GitHub Enterprise instance changed). You must delete the secret, update the URL, and then add the secret again. It’s a very minor change that likely won’t affect you. ---
**Author:** ![popac00](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@popac00](https://community.sonarsource.com/u/popac00)\ **Post date:** [August 13, 2024, 6:52am UTC](https://community.sonarsource.com/t/9-9-6-lta-release-notes/120083/3 "2024-08-13T06:52:39Z")
Hi Colin, This github secret that you’re saying is in the Sonarqube side? Thanks for replying! ---
**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\ **Post date:** [August 13, 2024, 10:05am UTC](https://community.sonarsource.com/t/9-9-6-lta-release-notes/120083/4 "2024-08-13T10:05:08Z")
Yes. It’s just saying that if you update the GitHub API URL, you must also update the private key at the same time. ![image](https://europe1.discourse-cdn.com/sonarsource/uploads/sonarcommunity/original/3X/d/8/d8a64e9ec35fe3ba52166c749cb45795645c2e9f.jpeg) ---
**Author:** ![popac00](https://avatars.discourse-cdn.com/v4/letter/p/6a8cbe/32.png) [@popac00](https://community.sonarsource.com/u/popac00)\ **Post date:** [August 20, 2024, 10:27am UTC](https://community.sonarsource.com/t/9-9-6-lta-release-notes/120083/5 "2024-08-20T10:27:55Z")
It’s me again, so am I correct in my understanding. As long as the github instance remains solid there shouldn’t be any issues with the current configuration? Am I correct? The only time that you need to change github secret is if the github instance (e.g. since the instance got changed, then the API of the URL should be changed as well) has been changed. ---
**Author:** ![Colin](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/colin/32/55255_2.png) [@Colin](https://community.sonarsource.com/u/Colin)\ **Post date:** [August 20, 2024, 11:30am UTC](https://community.sonarsource.com/t/9-9-6-lta-release-notes/120083/6 "2024-08-20T11:30:49Z")
That’s correct. It’s a really minor change.