fix(language-server): fedramp API URL construction #6433
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
PeterSchafer
approved these changes
Jan 15, 2026
ShawkyZ
changed the title
ShawkyZ
force-pushed
the
fix/ide-fedramp-uri-handling
branch
from
f69d7d8 to
35800c1
Compare
mihaibuzgau
pushed a commit
that referenced
this pull request
Jan 20, 2026
fix(language-server): fedramp API URL construction
mihaibuzgau
pushed a commit
that referenced
this pull request
Jan 20, 2026
fix(language-server): fedramp API URL construction (cherry picked from commit e085ccc)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Updates code-client-go to https://github.com/snyk/code-client-go/releases/tag/v1.24.6 to fix FedRAMP URI construction in the IDE.
Currently, if
api.snykgov.iois set in the IDE, it would result inapi.api.snykgov.ioThis fix addresses the URL normalization for this case.
Where should the reviewer start?
How should this be manually tested?
What's the product update that needs to be communicated to CLI users?